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

skaffold dev - deployment fails, but no events #3621

Closed
bukowa opened this issue Jan 31, 2020 · 3 comments
Closed

skaffold dev - deployment fails, but no events #3621

bukowa opened this issue Jan 31, 2020 · 3 comments
Labels
area/dev kind/question User question priority/p2 May take a couple of releases

Comments

@bukowa
Copy link

bukowa commented Jan 31, 2020

Expected behavior

I can see following message after "skaffold dev"

0/3 nodes are available: 3 node(s) didn't find available persistent volumes to bind.

Actual behavior

 - serviceaccount/commander-svc configured
 - role.rbac.authorization.k8s.io/commander-role configured
 - rolebinding.rbac.authorization.k8s.io/commander-role-binding configured
 - storageclass.storage.k8s.io/local-storage configured
 - persistentvolumeclaim/supplier-pvc configured
 - secret/x configured
 - deployment.apps/redis configured
Watching for changes...

Information

  • Skaffold version: v1.3.0
  • Operating system: Windows 10
  • Contents of skaffold.yaml:
apiVersion: skaffold/v2alpha3
kind: Config
metadata:
  name: myname
build:
  artifacts:
  - image: x/a
    context: commander
  - image: x/b
    context: supplier
deploy:
  kubectl:
    manifests:
    - deployment.yaml

Steps to reproduce the behavior

apiVersion: v1
kind: ServiceAccount
metadata:
  name: commander-svc
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: commander-role
rules:
  - apiGroups: [""]
    resources: ["pods"]
    verbs: ["create", "delete", "list"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: commander-role-binding
subjects:
  - kind: ServiceAccount
    name: commander-svc
roleRef:
  kind: Role
  apiGroup: rbac.authorization.k8s.io
  name: commander-role
---
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: local-storage
provisioner: kubernetes.io/no-provisioner
volumeBindingMode: WaitForFirstConsumer
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: supplier-pvc
spec:
  storageClassName: local-storage
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 30Gi
---
apiVersion: v1
kind: Secret
metadata:
  name: mysecret
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: redis
spec:
  replicas: 1
  selector:
    matchLabels:
      app: redis
  template:
    metadata:
      labels:
        app: redis
    spec:
      serviceAccountName: commander-svc

      volumes:
        - name: supplier-pvc
          persistentVolumeClaim:
            claimName: supplier-pvc

      containers:
        - name: redis
          image: redis:alpine
          ports:
            - containerPort: 6379

        - name: supplier
          image: x/b
          envFrom:
            - secretRef:
                name: mysecret
          volumeMounts:
            - mountPath: /supplier/supplies
              name: supplier-pvc
              subPath: supplier/supplies

        - name: commander
          image: x/a
          envFrom:
            - secretRef:
                name: mysecret
          volumeMounts:
            - mountPath: /supplier/supplies
              name: supplier-pvc
              subPath: supplier/supplies
          env:
            - name: NAMESPACE
              value: "default"
  1. skaffold dev
@bukowa bukowa changed the title skaffold dev - deployment fails, but no logs skaffold dev - deployment fails, but no events Jan 31, 2020
@tejal29
Copy link
Contributor

tejal29 commented Feb 3, 2020

@bukowa Can you use the --status-check flag with skaffold dev?

Were you expecting deployment failure events via skaffold Event API?

@bukowa
Copy link
Author

bukowa commented Feb 4, 2020

@tejal29 i had no chance to try again, do you still need any info? Thanks for the pull request!

@nkubala
Copy link
Contributor

nkubala commented Feb 29, 2020

I think this is fixed with the --status-check flag. i'm gonna close this issue for now, @bukowa please reopen if that doesn't help!

@nkubala nkubala closed this as completed Feb 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dev kind/question User question priority/p2 May take a couple of releases
Projects
None yet
Development

No branches or pull requests

3 participants