feat: Decouple cert-manager from base kubespray installation #1370
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zhmarvi
force-pushed
the
cert-manager-decouple
branch
from
ac37618 to
f551f9d
Compare
zhmarvi
force-pushed
the
cert-manager-decouple
branch
from
f551f9d to
b2062a7
Compare
zhmarvi
force-pushed
the
cert-manager-decouple
branch
from
b2062a7 to
2a6ce62
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In an effort to allow for other base k8s installation models including Talos k8s rollout. Rackspace team plan to decouple the cert-manager installation from the base kubespray ansible roles and allow the official upstream charts to provide updates and patched image rollouts. This includes gateway-api support and custom DNS server forwarders
issue link: #1344