This repository has been archived by the owner on Apr 10, 2024. It is now read-only.
fix: Explicitly Define Service Account Token in Pod Spec #36
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit addresses the issue described in GitHub titansoft-pte-ltd#31 where pods were unable to find the specified ConfigMap. By explicitly defining the service account token in the Pod specification, we ensure that the token is available to the Pod, thereby mitigating the issue. Related: titansoft-pte-ltd#31
|
Turned out my api server needed restarting |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR explicitly defines the service account token in the Pod specification to resolve an issue where Pods were failing due to a missing ConfigMap.
Related Issues
Fixes #31
Motivation
This change became necessary due to a provider-specific behavior observed in Kubernetes v1.27 on Civo (k3s), where the current manifest initially worked but later stopped functioning. Explicitly defining the token makes it consistently available to the Pod.
Technical Description
We modified the Pod specification to include an explicit reference to the service account token. This ensures that the Pod can access necessary resources, as outlined in issue #31.
Testing
Deployed the modified manifest in a Kubernetes v1.27 environment and verified that the Pod can now successfully locate the ConfigMap. I used terraform syntax so somebody might confirm my raw yaml is correct.
Additional Context
This modification aligns with emerging Kubernetes practices and appears to be the direction in which Kubernetes is heading. It's designed to be future-proof and to ensure the system remains robust against evolving provider-specific behaviors.