Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for additional certificate SANs #75

Merged
merged 3 commits into from
Jul 9, 2022

Conversation

prometherion
Copy link
Member

Closes #59.

This must be considered a breaking change, although Tenant Control Plane API is still `v1alpha1.

To preserve backward compatibility, change the value of the field tcp.spec.networkProfile.domain as element of the new field array, tcp.spec.networkProfile.certSANs.

Removing the field tcp.spec.networkProfile.domain in favor of the
tcp.spec.networkProfile.certSANs which allows specifying additional
extra domains that could be used to reach out to the tenant control
plane.
Copy link
Member

@bsctl bsctl left a comment

Choose a reason for hiding this comment

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

CN in certificate should include the complete name of the TCP

certSANs:
- ${TENANT_NAME}.${TENANT_DOMAIN}

docs/kamaji-azure-deployment-guide.md Outdated Show resolved Hide resolved
docs/kamaji-tenant-deployment-guide.md Outdated Show resolved Hide resolved
@prometherion prometherion requested a review from bsctl July 9, 2022 08:23
@prometherion prometherion merged commit c478753 into clastix:master Jul 9, 2022
@prometherion prometherion deleted the issues/59 branch July 9, 2022 08:49
@prometherion prometherion mentioned this pull request Sep 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Making optional spec.networkProfile.domain and renaming it to certSANs
2 participants