feat(provider): add NginxIngressRegistry parameter for Nginx Ingress Controller registry configuration #120
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.
Summary:
Introduced
NginxIngressRegistry
parameter to specify the container registry for Nginx Ingress Controller, with updates across all language SDKs and schema.Key points:
NginxIngressRegistry
toClusterArgs
inprovider/pkg/provider/cluster.go
.NginxIngressRegistry
isregistry.k8s.io
.NewCluster
function to useNginxIngressRegistry
for Nginx Ingress Controller image registry.schema.yaml
with description and default value.NginxIngressRegistry
.Generated with ❤️ by ellipsis.dev