gefyra-run: warn (or even stop) on active HPA config

[crkurz]

What happened?

Bridging a service which has active HPA config (.spec.maxReplicas>1) is likely to break bridge setup on next HPA scaling operation. This then causes invalid bridge state in Gefyra with the need for manual cleanup.

The root cause is that HPA will interfere with pod configurations already altered by Gefyra-bridge command. Be it on on scale-down or be it on scale-up.

What did you expect to happen?

Until Gefyra-bridge has support for cooperating with HPA, gefyra-bridge should error out when HPA config with .spec.maxReplicas>1 is detected.

Optionally user may decide to ignore the error.

Please provide the output of gefyra check.

.

How can we reproduce it (as minimally and precisely as possible)?

.

What Kubernetes setup are you working with?

$ kubectl version
# paste output here

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Anything else we need to know?

No response