[virtual-kubelet] Allow scheduling pods with name > 63 chars

[fra98]

Description

Fix #3093

As part of reflecting K8s pods, Liqo creates a new secret that holds the service account token from the consumer cluster. This secret has a particular label with the key "virtualkubelet.liqo.io/service-account-for-pod-name" and value of the original pod name. This causes an issue when the pod name is longer than 63 characters, where the resulting k8s secret cannot be created due to kubernetes limitations on max lenght of label values.

This artificially limits the size of pod names that can be reflected by Liqo to 63 instead of the 253 characters, which is allowed by Kubernetes.

This PR fixes the issue by changing how the secret is forged. Instead of relying on labels, the key is moved to annotations, which do NOT present any limitations on value length.

[adamjensenbot]

Hi @fra98. Thanks for your PR!

I am @adamjensenbot.
You can interact with me issuing a slash command in the first line of a comment.
Currently, I understand the following commands:

• /rebase: Rebase this PR onto the master branch (You can add the option test=true to launch the tests
  when the rebase operation is completed)
• /merge: Merge this PR into the master branch
• /build Build Liqo components
• /test Launch the E2E and Unit tests
• /hold, /unhold Add/remove the hold label to prevent merging with /merge

Make sure this PR appears in the liqo changelog, adding one of the following labels:

• feat: 🚀 New Feature
• fix: 🐛 Bug Fix
• refactor: 🧹 Code Refactoring
• docs: 📝 Documentation
• style: 💄 Code Style
• perf: 🐎 Performance Improvement
• test: ✅ Tests
• chore: 🚚 Dependencies Management
• build: 📦 Builds Management
• ci: 👷 CI/CD
• revert: ⏪ Reverts Previous Changes

[fra98]

/test

[fra98]

/rebase test=true

[aleoli]

/test

[claudiolor]

/merge