Kapp deploy command changing K8S ServiceAccount label value
- Dominant language
- Go
- Stars
- 1.1k
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Description
**What steps did you take:**
1. Ran `kapp deploy -a --diff-run --diff-changes=true -f ./app.yaml --into-ns --namespace --default-label-scoping-rules=false`.
**What happened:**
The value of _**ServiceAccount**_ label was changed/converted when I ran `kapp deploy` command.
**Original manifest in K8S:**
```
apiVersion: v1
kind: ServiceAccount
metadata:
name: app-name
labels:
github.com/sha-short: "1b85fe5e"
...
```
**New manifest to be deployed in K8S:**
```
apiVersion: v1
kind: ServiceAccount
metadata:
name: app-name
labels:
github.com/sha-short: "934881e3"
...
```
The new value of _**github.com/sha-short**_ label is being changed/converted to "934881**000**" instead "934881**e3**".
**What did you expect:**
The _**github.com/sha-short**_ label continues using the label as defined in the manifest.
**Anything else you would like to add:**
If you change the final of the value for "e1", "e2", "e4", `kapp` command will change/convert to "0", "00", "0000" respectively.
**Environment:**
- kapp version (use `kapp --version`): 0.62.1
- OS (e.g. from `/etc/os-release`): MacOs 14.5 (23F79) and Ubuntu 22.04.4
- Kubernetes version (use `kubectl version`): v1.30.2
---
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.
Contributor guide
Assessment
This issue has not been assessed yet.