Configuring Projected volume with pod is always in CrashLoopBackoff State

[niranjandarshann]

Page related to the issue: https://kubernetes.io/docs/concepts/storage/projected-volumes/#example-configuration-secrets-nondefault-permission-mode
When i am creating a projected volume having two secrets mysecret and mysecret1 at the location /project-volume/my-guide/my-username and /project-volume/my-guide/my-password the secret get created perfectly and when i create a pod it get created but remain in CrashLoopBackoff State.
Whether i am missing any thing or is there any problem with the file.

I am attaching the whole process i do:

File Location

Created Secrets

Yaml file of Pod

Final Output

Your opinion and help means a lot to me.

Proposed solution :
The pods should go in Ready state.

[k8s-ci-robot]

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

• /sig <group-name>
• /wg <group-name>
• /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

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.

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

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.

[niranjandarshann]

/language en
/kind support

[k8s-ci-robot]

@niranjandarshann: The label(s) language/en cannot be applied, because the repository doesn't have them.

In response to this:

/language en
/kind support

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.

[tamilselvan1102]

By default, a pod’s restart policy is Always, meaning it should always restart on failure (other options are Never or OnFailure). Depending on the restart policy defined in the pod template, Kubernetes might try to restart the pod multiple times.

Every time the pod is restarted, Kubernetes waits for a longer and longer time, known as a “backoff delay”. During this process, Kubernetes displays the CrashLoopBackOff error.

[niranjandarshann]

By default, a pod’s restart policy is Always, meaning it should always restart on failure (other options are Never or OnFailure). Depending on the restart policy defined in the pod template, Kubernetes might try to restart the pod multiple times.

Every time the pod is restarted, Kubernetes waits for a longer and longer time, known as a “backoff delay”. During this process, Kubernetes displays the CrashLoopBackOff error.

@tamilselvan1102 thank you, but here i am looking for whats wrong in the process i am doing.
How to create a pod with projected volume must be in Ready state instead of CrashLoopBackoff.

[niranjandarshann]

I am attaching the description of the pods volume-test.

[killshotrevival]

Hey @niranjandarshann , I believe the issue is not with the volumes, but with the image, you are using, busy box as the image, but as there is no process that keeps the container running, the pod is completing, as you can see in your first screenshot, and after that it is going to crashloopback state.

To keep a container running you can try something like:

  - name: container-test
    image: busy box
    command: ["sleep", "3600"]

This will start a sleep process in your busybox, that will keep the container running for 1 hr. Hope this help 😃

[niranjandarshann]

Hey @niranjandarshann , I believe the issue is not with the volumes, but with the image, you are using, busy box as the image, but as there is no process that keeps the container running, the pod is completing, as you can see in your first screenshot, and after that it is going to crashloopback state.

To keep a container running you can try something like:

  - name: container-test
    image: busybox
    command: ["sleep", "3600"]

This will start a sleep process in your busybox, that will keep the container running for 1 hr. Hope this help smiley

@killshotrevival Thank you for your support now the pod is running by adding command labels in my yaml file.

[niranjandarshann]

closing the issue marking it as resolved
/close

[k8s-ci-robot]

@niranjandarshann: Closing this issue.

In response to this:

closing the issue marking it as resolved
/close

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.