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

with minikube 1.4.0.beta #1166

Closed
kvokka opened this issue Sep 8, 2019 · 0 comments · Fixed by #1178
Closed

with minikube 1.4.0.beta #1166

kvokka opened this issue Sep 8, 2019 · 0 comments · Fixed by #1178
Assignees
Labels
bug priority:medium Medium priority issue or feature

Comments

@kvokka
Copy link

kvokka commented Sep 8, 2019

Bug

Current Behavior

garden deploy

[2019-09-08T05:29:17.561Z] Error: Unrecognized resource type extensions/v1beta1/Deployment
    at KubeApi.<anonymous> (/snapshot/dist/build/src/plugins/kubernetes/api.js:0)
    at Generator.next (<anonymous>)
    at fulfilled (/snapshot/dist/build/src/plugins/kubernetes/api.js:0)
Error Details:
manifest:
  apiVersion: extensions/v1beta1
  kind: Deployment
  metadata:
    creationTimestamp: null
    labels:
      app: helm
      name: tiller
    name: tiller-deploy
    namespace: demo-project
  spec:
    replicas: 1
    strategy: {}
    template:
      metadata:
        creationTimestamp: null
        labels:
          app: helm
          name: tiller
      spec:
        automountServiceAccountToken: true
        containers:
          - env:
              - name: TILLER_NAMESPACE
                value: demo-project
              - name: TILLER_HISTORY_MAX
                value: '0'
            image: 'gcr.io/kubernetes-helm/tiller:v2.14.1'
            imagePullPolicy: IfNotPresent
            livenessProbe:
              httpGet:
                path: /liveness
                port: 44135
              initialDelaySeconds: 1
              timeoutSeconds: 1
            name: tiller
            ports:
              - containerPort: 44134
                name: tiller
              - containerPort: 44135
                name: http
            readinessProbe:
              httpGet:
                path: /readiness
                port: 44135
              initialDelaySeconds: 1
              timeoutSeconds: 1
            resources: {}
        serviceAccountName: garden-tiller
  status: {}


[2019-09-08T05:29:17.579Z] Error: Failed resolving one or more provider configurations:
- local-kubernetes: Unrecognized resource type extensions/v1beta1/Deployment
    at Garden.<anonymous> (/snapshot/dist/build/src/garden.js:0)
    at Generator.next (<anonymous>)
    at fulfilled (/snapshot/dist/build/src/garden.js:0)
Error Details:
rawConfigs:
  - name: exec
  - name: container
  - name: local-kubernetes
    environments:
      - local
taskResults:
  resolve-provider.exec:
    type: resolve-provider
    key: resolve-provider.exec
    name: exec
    description: resolving provider exec
    output:
      name: exec
      dependencies: []
      moduleConfigs: []
      config:
        name: exec
        path: /Users/mike/tmp/garden/examples/demo-project
      status:
        ready: true
        outputs: {}
    dependencyResults: {}
  resolve-provider.container:
    type: resolve-provider
    key: resolve-provider.container
    name: container
    description: resolving provider container
    output:
      name: container
      dependencies: []
      moduleConfigs: []
      config:
        name: container
        path: /Users/mike/tmp/garden/examples/demo-project
      status:
        ready: true
        outputs: {}
    dependencyResults: {}
  resolve-provider.local-kubernetes:
    type: resolve-provider
    description: resolving provider local-kubernetes
    key: resolve-provider.local-kubernetes
    name: local-kubernetes
    error:
      detail:
        manifest:
          apiVersion: extensions/v1beta1
          kind: Deployment
          metadata:
            creationTimestamp: null
            labels:
              app: helm
              name: tiller
            name: tiller-deploy
            namespace: demo-project
          spec:
            replicas: 1
            strategy: {}
            template:
              metadata:
                creationTimestamp: null
                labels:
                  app: helm
                  name: tiller
              spec:
                automountServiceAccountToken: true
                containers:
                  - env:
                      - name: TILLER_NAMESPACE
                        value: demo-project
                      - name: TILLER_HISTORY_MAX
                        value: '0'
                    image: 'gcr.io/kubernetes-helm/tiller:v2.14.1'
                    imagePullPolicy: IfNotPresent
                    livenessProbe:
                      httpGet:
                        path: /liveness
                        port: 44135
                      initialDelaySeconds: 1
                      timeoutSeconds: 1
                    name: tiller
                    ports:
                      - containerPort: 44134
                        name: tiller
                      - containerPort: 44135
                        name: http
                    readinessProbe:
                      httpGet:
                        path: /readiness
                        port: 44135
                      initialDelaySeconds: 1
                      timeoutSeconds: 1
                    resources: {}
                serviceAccountName: garden-tiller
          status: {}
      type: kubernetes
messages:
  - '- local-kubernetes: Unrecognized resource type extensions/v1beta1/Deployment'

Suggested solution(s)

Update Deployment to v1

Additional context

using minikube 1.4.0 (with k8s 1.16) get an error. Looks like k8s 1.16 deprecated Deployment/v1beta1

with minikube 1.3.1 ( with k8s 1.15.2) everything works.

Your environment

garden version
0.10.8

kubectl version
1.15.2
docker version
Docker version 19.03.2, build 6a30dfc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug priority:medium Medium priority issue or feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants