This helm attempts to verify the API version during deployment processes. However, in some environments, direct access to the API is not available beforehand, which complicates the deployment.
This situation is particularly problematic in two notable scenarios:
Offline Manifest Generation and Application: When the manifests are generated in one environment (e.g., a CI/CD pipeline or a local machine) and then applied to another cluster, there's no way to verify the API version during the generation phase.
Manifest Generation Using Kustomize: In environments where manifests are created using tools like kustomize, the version check becomes redundant and can lead to deployment issues.
My PR proposes modifications that bypass the API version check under these specific conditions, ensuring smoother and more flexible deployments in environments lacking direct API connectivity.
What this PR does / why we need it:
This helm attempts to verify the API version during deployment processes. However, in some environments, direct access to the API is not available beforehand, which complicates the deployment.
This situation is particularly problematic in two notable scenarios:
My PR proposes modifications that bypass the API version check under these specific conditions, ensuring smoother and more flexible deployments in environments lacking direct API connectivity.
Checklist
[stable/mychartname]
)