You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have several changes we make to the helm chart on the cluster to deal with container registry and image issues.
We make these changes on the cluster using mutating hooks. Specifically we use the following:
After post-rendering stage mutations could be made before the rendered manifest is applied to the cluster. These changes also would be part of the logic to compare deployed manifest with Git Repo so that mutations are made before comparison.
Motivation
We have use case where we are running our own private repo and want to use third party charts where the container registry is not in the values file to override. The standard helm chart template when created has the registry and image combined:
image:
repository: nginxpullPolicy: IfNotPresent# Overrides the image tag whose default is the chart appVersion.tag: ""
The other problem that the registry-cred webhook address is making sure that the ImagePullSecrets are configured in the namespace. This is needed to make our private registry work with third party charts. In clusters that are not in production and have access to dockerhub we started to experience access issues due to rate limiting changes that took effect recently. So we are configuring an account for dockerhub so that we are not rate limited on access.
Proposal
If these changes are of interest we could evaluate submitting a PR for the changes.
The text was updated successfully, but these errors were encountered:
Summary
We have several changes we make to the helm chart on the cluster to deal with container registry and image issues.
We make these changes on the cluster using mutating hooks. Specifically we use the following:
After post-rendering stage mutations could be made before the rendered manifest is applied to the cluster. These changes also would be part of the logic to compare deployed manifest with Git Repo so that mutations are made before comparison.
Motivation
Proposal
If these changes are of interest we could evaluate submitting a PR for the changes.
The text was updated successfully, but these errors were encountered: