-
Notifications
You must be signed in to change notification settings - Fork 326
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
injection stack traces when deploying multi-port application #1594
Comments
Hi @darkn3rd, Thank you for opening this issue. This is a known limitation of multiport deployments as listed in the "Caveats for Multiport Pods" section of the Connect docs: https://www.consul.io/docs/k8s/connect#caveats-for-multi-port-pods Best, |
@t-eckert The fact that I got feedback in the logs and such was great, that helped me understand the issue at hand. Thanks for the doc link. You know when metrics will be supported with multi-port? or will multi-port get greater support later? |
We don't have anything definitive yet, but it's definitely something we're going to look into soon! |
Pinging to keep this alive. Let me know if anything will be added to the roadmap |
Pinging to keep this alive again, so automation doesn't erase this issue. |
@darkn3rd, thank you for your commitment to this issue. I can assure you that we don't have automation that will erase this issue and we are tracking it internally as we plan our roadmap for Consul on Kubernetes. When we plan to address this, you will certainly be kept appraised. |
@t-eckert Thank you. That's promising. I remember some important issue in another project (Terraform) were closed and never addressed, which was demoralizing. I am glad that is not the case here, very positive. Also, I talked with the PM on this at the recent HashiConf23 in SF, so I am glad about the new developments with the new schema for the v2 service catalog. |
Good to hear! V2 will bring huge improvements to Multiport that we are excited about. |
Community Note
Overview of the Issue
Cannot deploy multi-port application with metrics enabled. The StatefulSet returns this event:
Reproduction Steps
Overview of Steps:
NOTE: I can provide step-by-step to reproduce this, but since this is easy to reproduce, gave the minimal steps.
Logs
Consul Connect Logs
Expected behavior
I expected that I would be able to deploy a multi-port application and be able to use metrics, and I expected that there would be errors with the consul-connect-injector.
Environment details
Additionally, please provide details regarding the Kubernetes Infrastructure, as shown below:
The text was updated successfully, but these errors were encountered: