Skip to content

Conversation

@pooknull
Copy link
Contributor

@pooknull pooknull commented Jul 23, 2025

K8SPXC-1494 Powered by Pull Request Badge

https://perconadev.atlassian.net/browse/K8SPXC-1494

DESCRIPTION

This PR adds a .spec.tls.certValidityDuration and .spec.tls.caValidityDuration fields to the cr.yaml. These fields control the validity period of the TLS certificates generated by the operator

CHECKLIST

Jira

  • Is the Jira ticket created and referenced properly?
  • Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
  • Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

  • Is an E2E test/test case added for the new feature/change?
  • Are unit tests added where appropriate?
  • Are OpenShift compare files changed for E2E tests (compare/*-oc.yml)?

Config/Logging/Testability

  • Are all needed new/changed options added to default YAML files?
  • Are all needed new/changed options added to the Helm Chart?
  • Did we add proper logging messages for operator actions?
  • Did we ensure compatibility with the previous version or cluster upgrade process?
  • Does the change support oldest and newest supported PXC version?
  • Does the change support oldest and newest supported Kubernetes version?

@pull-request-size pull-request-size bot added the size/M 30-99 lines label Jul 23, 2025
@hors hors added this to the v1.19.0 milestone Jul 29, 2025
Copy link
Contributor

@egegunes egegunes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pooknull please add PR description and check golangci-lint errors

Group: issuerGroup,
},
Duration: &metav1.Duration{Duration: pxctls.DefaultValidity},
Duration: duration,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so when i set validity duration all certs will be valid for this duration, including CA. i wonder if this will make rotation harder when these certs are expired. in PSMDB operator, we don't use this field for CA cert and hardcode 365 days for its validity duration (i don't think that approach is correct either bc what happens if user specifies 366 days for cert validity?). maybe we need to have a separate field for CA validity duration?

@hors wdyt?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am ok to add a separate field for CA validity duration

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pull-request-size pull-request-size bot added size/L 100-499 lines and removed size/M 30-99 lines labels Nov 11, 2025
@pooknull pooknull marked this pull request as ready for review November 12, 2025 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/L 100-499 lines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants