kustomize
kustomize copied to clipboard
kubernetes-sigs
Not work with remote repo
Kustomize version: {Version:unknown GitCommit:$Format:%H$ BuildDate:1970-01-01T00:00:00Z GoOs:linux GoArch:amd64} as i expected version is the latest because it was installed from here: https://kubectl.docs.kubernetes.io/installation/kustomize/source/#install-the-kustomize-cli-from-local-source-with-cloning-the-repo with version v4.5.2.
I have the next file structure:
It works well using kustomize build from local files like this:
But when i use remote git url it crashes with error:
Unable to create application: application spec is invalid: InvalidSpecError: Unable to get app details: rpc error: code = Unknown desc = `kustomize build /tmp/[email protected]_retainly-bitb_k8s/k8s/overlays/dev`
failed exit status 1: Error: accumulating resources: accumulation err='accumulating resources from './../../base': '/tmp/[email protected]_retainly-bitb_k8s/k8s/base' must resolve to a file':
recursed accumulation of path '/tmp/[email protected]_retainly-bitb_k8s/k8s/base': accumulating resources:
accumulation err='accumulating resources from 'core': '/tmp/[email protected]_retainly-bitb_k8s/k8s/base/core' must resolve to a file':
recursed accumulation of path '/tmp/[email protected]_retainly-bitb_k8s/k8s/base/core': accumulating resources: accumulation err='accumulating resources from
'services/core-api-service.yaml': evalsymlink failure on '/tmp/[email protected]_retainly-bitb_k8s/k8s/base/core/services/core-api-service.yaml'
: lstat /tmp/[email protected]_retainly-bitb_k8s/k8s/base/core/services: no such file or directory': evalsymlink failure on
'/tmp/[email protected]_retainly-bitb_k8s/k8s/base/core/services/core-api-service.yaml' : lstat /tmp/[email protected]_retainly-bitb_k8s/k8s/base/core/services: no such file or directory
So the question is why it not works with remote files? For now i try to use ArgoCD with my kustomize manifest files, but it not work.
@Spartaques: This issue is currently awaiting triage.
SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/triage needs-information
Can you please provide the Kustomization you're working with and the directory structure (or even better, the entire sample that is not working for you)?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten