skaffold
skaffold copied to clipboard
Easy and Repeatable Kubernetes Development
Skaffold verify hangs when using --event-log-file w/ dir that doesn't exist. Other commands (eg: render, etc) don't hang out display an error ``` open /ccd-start-project/somerandom/output: no such file or directory...
### Expected behavior The `skaffold.yaml` configuration for the `googleCloudBuild` remote builder, supports configuring extended builder image parameters/arguments to be passed into the builder image. ie, config that passes through to...
### Expected behavior k8s manifest files to be generated ### Actual behavior Intermittently getting: deployment/django: container arthur-production-django terminated with exit code 2 pod/django-697ddc88b9-hks6r: container arthur-production-django terminated with exit code 2...
### Expected behavior When run in [Github Actions](https://github.com/iamnoah/skaffold-tput-colors-bug/actions/runs/2463260647/workflow), `skaffold build` does not fail with a valid configuration, or fails with a clear error. ### Actual behavior In the GitHub Actions...
Currently Skaffold V2 has the concept of a "hydration-directory" that can be assumed to exist across stages or when deleting. There is currently no requirements on when this "hydration-directory" should...
### Discussion - Kustomize deployer is not used in v2, and we've moved Kustomize manifests logic into generate.go should we remove Kustomize deployer?
## Background - #7515 changed init cmd behavior to generate skaffold.yaml fits v3alphal1 schema - If kustomize, raw manifests detected or cli provide manifests, generated skaffold config will have render...
##Description integration some tests in integration/generate_pipeline_test.go were temporarily disabled due to v2 migration without completing v2 render Some disabled tests may fail when enabling it due to test skaffold.yaml don't...
Currently skaffold is preparing it's first skaffold v2 release - `skaffold-v2-alpha-1`. During this period where the skaffold team is improving skaffold v2 and there is a v1 and v2 split,...
The v2 kubectl renderer doesn't do anything besides image replacement, where as the old kubectl deployer's render function would run `kubectl create --dry-run` against the cluster, which I believe added...