Comments (20)
It has to be patched in Kubernetes repo & released in GKE, here's the issue you can track: kubernetes/kubernetes#54583
Until then, if it bothers you, you can exclude these logs from Stackdriver
from k8s-stackdriver.
@loburm +1, could you please remove it/make it Info.V(2)
?
from k8s-stackdriver.
This already fixed in the code. (Replaced by Info.V(4))
But I still need to push a new image of prometheus-to-sd and update image version in the code after that.
from k8s-stackdriver.
OK, thanks, looking forward to it
from k8s-stackdriver.
Thanks for the quick info, will this be available in a new patch release, or is this independent from Kubernetes itself?
from k8s-stackdriver.
One way is to update image version manually in yaml file. Then addon manager will redeploy it.
from k8s-stackdriver.
One way is to update image version manually in yaml file. Then addon manager will redeploy it.
This is not possible in GKE
@mbertschler Yes, it most probably will be available in one of the future patch releases, though there's no ETA yet
from k8s-stackdriver.
Sorry, missed that it's related to GKE. In such case patch release is required. Once it's going to be available I'll post an update here.
from k8s-stackdriver.
@crassirostris @loburm Thanks for the quick help, now that I know it will be fixed and is not actually an error on my side I can live with the situation for now. :)
from k8s-stackdriver.
I have released prometheus-to-sd v0.2.2 that have better logging. Feel free to try it.
from k8s-stackdriver.
@loburm we are also seeing this with one of our flask apps, any clues on how to fix?
from k8s-stackdriver.
Could you be more explicit here? If you are using prometheus-to-sd and seeing a lot of such warnings, then you should just switch to the newer version.
from k8s-stackdriver.
Not on purpose at least...we have enabled stackdriver logging via our google cloud console for our gke clusters. In the last 24 hours our logs are looking like this:
from k8s-stackdriver.
@Dakuan what is your GKE Kubernetes version on the node pool?
from k8s-stackdriver.
heya @mbertschler its 1.7.8
from k8s-stackdriver.
Perfect, thanks!
from k8s-stackdriver.
Observed the log spam on 1.9.2-gke.1, it was working fine while in 1.8.7-gke.1.
from k8s-stackdriver.
@shantuo is it coming from prometheus-to-sd that is a side container for kube-dns? If yes, then fix is already submitted, and everything should work fine in 1.9.3.
from k8s-stackdriver.
It is from prometheus-to-sd container. I tried with 1.9.3-gke.0 and still saw this.
from k8s-stackdriver.
Saw this again in 1.9.6-gke.0.
from k8s-stackdriver.
Related Issues (20)
- prometheus-to-sd | 403 Permission error, with correct Service Account permissions. HOT 2
- Custom stack driver pod doesnt seem to have liveness/readiness probe.
- Running custom-metrics-stackdriver-adapter as non-root user HOT 1
- Stackdriver metrics are not supported by HorizontalPodAutoscaler HOT 2
- ClusterRole in stackdriver adapter has namespace defined
- custom-metrics-stackdriver-adapter not working - auth problems? HOT 13
- Security Policy violation Binary Artifacts HOT 5
- Allow custom metrics from a different pod HOT 3
- Custom metrics adapter spewing errors "apiserver was unable to write a fallback JSON response: http2: stream closed" HOT 11
- custom-metrics-stackdriver-adapter - couldn't get resource list for external.metrics.k8s.io/v1beta1: Got empty response for: external.metrics.k8s.io/v1beta1 HOT 2
- istio.io/service/server/response_latencies metric that HPA collected is different to Cloud monitoring HOT 1
- Filtering metrics by labelSelector in external.metrics.k8s.io api doesn't work HOT 1
- Timeout error logs HOT 5
- Deploying adapter_new_resource_model.yaml results in OOMKilled HOT 3
- 100% memory and CPU and never recovers HOT 2
- Documentation bugs in custom-metrics-stackdriver-adapter README HOT 3
- Error while sending request to Stackdriver googleapi: Error 503 HOT 17
- Tracing custom-metrics-stackdriver-adapter trace logging enabled HOT 6
- wrong version of file in tag HOT 4
- Unable to authenticate the request err="verifying certificate failed: x509: certificate signed by unknown authority"" HOT 3
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 k8s-stackdriver.