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

helm does not perform upgrade #4399

Closed
MarcoSchaar opened this issue Jun 26, 2020 · 3 comments
Closed

helm does not perform upgrade #4399

MarcoSchaar opened this issue Jun 26, 2020 · 3 comments

Comments

@MarcoSchaar
Copy link

Expected behavior

deploy and upgrade helm charts worked fine with version 1.10.1 and api v2beta4

Actual behavior

helm does not perform an upgrade with version 1.11 / 1.12 and api v2beta5

Information

  • Skaffold version: 1.11 / 1.12
  • Operating system: any
  • Contents of skaffold.yaml:
apiVersion: skaffold/v2beta5
kind: Config
metadata:
  name: some-name
profiles:
  - name: dev
    deploy:
      kubeContext: clustername
      helm:
        releases:
        - name: dev-ingress
          chartPath: stable/nginx-ingress
          valuesFiles: 
          - helm-values/dev/nginx_values.yaml
          namespace: dev
          remote: true
          recreatePods: true
      kubectl:
        manifests:
        - kubernetes-manifests/dev/namespace.yaml
        - kubernetes-manifests/dev/secret.yaml
        - kubernetes-manifests/dev/deployment.yaml
        - kubernetes-manifests/dev/service.yaml
        - kubernetes-manifests/dev/ingress.yaml

Steps to reproduce the behavior

  1. compare with version 1.10.1
  2. skaffold run --profile <profile>

related logs:

level=debug msg="Running command: [helm version --client]"
level=info msg="Deploying with helm v2.16.8 ..."
level=debug msg="Running command: [helm --kube-context clustername get dev-ingress]"
level=info msg="Release dev-ingress not upgraded as it is remote..."
@MarcoSchaar
Copy link
Author

could be related to
#4294

@Mor-Walkme
Copy link

Adding "upgradeOnChange: true" to skaffold.yaml solved the issue for me

@MarcoSchaar
Copy link
Author

Thanks @Mor-Walkme
that helped for me as well.
somehow behavior has changed.

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

No branches or pull requests

2 participants