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.

Sign up for GitHub

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

Jump to bottom

kctrl package release does not work as expected inside a kubernetes pod #1627

Open
rohitagg2020 opened this issue Sep 20, 2024 · 2 comments · May be fixed by #1638
Open

kctrl package release does not work as expected inside a kubernetes pod #1627

rohitagg2020 opened this issue Sep 20, 2024 · 2 comments · May be fixed by #1638
Assignees
@devanshuVmware
Labels
bug This issue describes a defect or unexpected behavior carvel-accepted This issue should be considered for future work and that the triage process has been completed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@rohitagg2020
Copy link
Contributor

What steps did you take:

  1. Added kctrl as binary to the Dockerfile.
  2. Created a container image.
  3. Deployed a pod with the above image.
  4. Ssh into the pod.
  5. Ran 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.
Screenshot 2024-09-10 at 8 05 28 PM

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.
@rohitagg2020 rohitagg2020 added bug This issue describes a defect or unexpected behavior carvel-triage This issue has not yet been reviewed for validity labels Sep 20, 2024
@renuy renuy added carvel-accepted This issue should be considered for future work and that the triage process has been completed and removed carvel-triage This issue has not yet been reviewed for validity labels Sep 20, 2024
@renuy renuy added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Sep 20, 2024
@madAndroid
Copy link

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

@100mik
Copy link
Contributor

100mik commented Oct 17, 2024

Taking a closer look, in case of kapp we would escape here. But for whatever reason this condition is not true. We should not be running kapp here at all.

Judging from the output the path is user/local/bin/kapp in which case this condition should evaluate to true.
To figure out why it is not evaluating accurately, we probably need to build a binary logging more information, and test it in the same environment.

@devanshuVmware devanshuVmware linked a pull request Nov 5, 2024 that will close this issue
Open
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@devanshuVmware devanshuVmware

Labels
bug This issue describes a defect or unexpected behavior carvel-accepted This issue should be considered for future work and that the triage process has been completed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
Carvel
Status: Unprioritized
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Return from RunWithCancel if cmd is kapp devanshuVmware/kapp-controller
5 participants
@renuy @madAndroid @100mik @rohitagg2020 @devanshuVmware