What happened:
When I am trying to run kctrl pkg release inside the k8s pod, it errors out.
What did you expect:
Expected kctrl pkg release to complete successfully and produce the carvel-artifacts.
Anything else you would like to add:
[Additional information that will assist in solving the issue.]
Environment:
kapp Controller version (execute kubectl get deployment -n kapp-controller kapp-controller -o yaml and the annotation is kbld.k14s.io/images):
Kubernetes version (use kubectl version)
Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.
We're experiencing this as well - it seems any KUBECONFIG related environment variables are being ignored, and the internal K8s environment variables are being used instead
What steps did you take:
kctrl
as binary to the Dockerfile.kctrl pkg release
inside the k8s pod.What happened: When I am trying to run
kctrl pkg release
inside the k8s pod, it errors out.What did you expect: Expected
kctrl pkg release
to complete successfully and produce thecarvel-artifacts
.Anything else you would like to add: [Additional information that will assist in solving the issue.]
Environment:
kubectl get deployment -n kapp-controller kapp-controller -o yaml
and the annotation iskbld.k14s.io/images
):kubectl version
)Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible" 👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.