Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Controller uses autoscaling v2 instead of v2beta1 when necessary #114

Closed

Conversation

voelzmo
Copy link
Member

@voelzmo voelzmo commented Nov 21, 2022

What this PR does / why we need it:
Builds on #112 and adds the necessary controller changes to not use autoscaling v2beta1 when it is not available.

Which issue(s) this PR fixes:
Fixes #104

Special notes for your reviewer:
This is just pushed as a WIP in case we need this code at a later point in time.

Release note:


@gardener-robot gardener-robot added needs/review Needs review size/xl Size of pull request is huge (see gardener-robot robot/bots/size.py) needs/second-opinion Needs second review by someone else labels Nov 21, 2022
@gardener-robot-ci-2 gardener-robot-ci-2 added the reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) label Nov 21, 2022
@voelzmo
Copy link
Member Author

voelzmo commented Nov 21, 2022

Closing this: #104 (comment)

@voelzmo voelzmo closed this Nov 21, 2022
@gitguardian
Copy link

gitguardian bot commented Nov 21, 2022

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id Secret Commit Filename
- Generic Private Key 2e0deea config/certs/rootCA-key.pem View secret
- Generic Private Key 2e0deea config/certs/tls.key View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!

@gardener-robot gardener-robot added the status/closed Issue is closed (either delivered or triaged) label Nov 21, 2022
@gardener-robot-ci-2 gardener-robot-ci-2 added needs/ok-to-test Needs approval for testing (check PR in detail before setting this label because PR is run on CI/CD) and removed reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) labels Nov 21, 2022
@voelzmo
Copy link
Member Author

voelzmo commented Nov 21, 2022

Just for completeness sake: the above credentials are self-signed certificates for localhost used for testing the controller.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs/ok-to-test Needs approval for testing (check PR in detail before setting this label because PR is run on CI/CD) needs/review Needs review needs/second-opinion Needs second review by someone else size/xl Size of pull request is huge (see gardener-robot robot/bots/size.py) status/closed Issue is closed (either delivered or triaged)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feature] Handle autoscaling/v2 API version for HorizontalPodAutoscaler
3 participants