Comments (13)
Acked, I will add new release with the latest image from distroless.
from cluster-proportional-autoscaler.
Update, the change to fix the vulnerability has been merged: kubernetes/kubernetes#98401
I do not see new images published yet however, will keep an eye out for that.
from cluster-proportional-autoscaler.
Yes this was resolved in release 1.8.4 and can be closed out.
from cluster-proportional-autoscaler.
@jonesbr17 Thanks for reporting. I'm not sure about which versions are impacted as I don't find any import of the tzdata package. Also CPA doesn't use debian as the base image IFAICT. Could you give more context? Thanks.
from cluster-proportional-autoscaler.
I'm seeing the issue on 1.8.3 as well as 1.7.1. From what I've seen, images built on distroless just need to be rebuilt to pick up the remedy.
from cluster-proportional-autoscaler.
There is a new release of gcr.io/distroless/static:nonroot
available, so publishing a new release at this point should resolve the vulnerabilities
from cluster-proportional-autoscaler.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
from cluster-proportional-autoscaler.
/remove-lifecycle stale
from cluster-proportional-autoscaler.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/stale
is applied - After 30d of inactivity since
lifecycle/stale
was applied,lifecycle/rotten
is applied - After 30d of inactivity since
lifecycle/rotten
was applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale
- Mark this issue or PR as rotten with
/lifecycle rotten
- Close this issue or PR with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
from cluster-proportional-autoscaler.
/remove-lifecycle stale
from cluster-proportional-autoscaler.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/stale
is applied - After 30d of inactivity since
lifecycle/stale
was applied,lifecycle/rotten
is applied - After 30d of inactivity since
lifecycle/rotten
was applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale
- Mark this issue or PR as rotten with
/lifecycle rotten
- Close this issue or PR with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
from cluster-proportional-autoscaler.
/remove-lifecycle stale
from cluster-proportional-autoscaler.
@jonesbr17 has this problem been resolved?
from cluster-proportional-autoscaler.
Related Issues (20)
- helm chart: add topologySpreadConstraints support HOT 4
- info: 1.8.7 tag but no release HOT 7
- Deprecation of legacy k8s.gcr.io container image registry HOT 6
- How does the maxReplicas field in HPA affect the algorithm?
- cluster-proportional-autoscaler is not rebalancing after spikes HOT 6
- Metrics endpoint HOT 6
- Facing vulnerability issues with golang , net packages HOT 4
- Request for Inclusion of Compatibility Matrix in README.md HOT 5
- tag for 1.8.8 includes v HOT 2
- Defaults matching PSS restricted HOT 6
- Re-build v1.8.8 to build with latest minor version of go 1.20 to fix CVEs HOT 12
- Changelog outdated HOT 3
- CPA does not support scale based on pod number HOT 4
- Image location in RELEASE.md is wrong HOT 7
- Allow horizontally scaling StatefulSets HOT 4
- [chart] Please support configuring environment variables for the container HOT 4
- Can't start pod issue HOT 4
- Missing 1.8.10 release HOT 4
- Request: Please make FIPS 140-2 compliant images available HOT 1
- Any way to disable when node(s) are being shutdown? HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cluster-proportional-autoscaler.