A group for app developers, platform engineering, and Portworx users around containers and Kubernetes.
Open Group
Cloud Native Events
Want to join us at an in-person event? Check the calendar here to see what's coming up near you.
Cloud Native Discussions
This usergroup is an inclusive place for folks that want to learn about containers, kubernetes, cloud technologies, and modern applications. Our goal is to foster a community of peers so we can learn from each other, learn about relevant technologies.Group Content
Cloud Native Summer Series: Exploring the Landscape
Cincinnati Cloud Native enthusiasts! We will be hosting a series of events this summer to grow the CNCF community locally. In our first event, we will be gathering for a roundtable discussion about the current landscape and what solutions you are building in this ecosystem right now. We will meet at the Callibrity offices in Montgomery at 8280 Montgomery Rd at 3pm. Food and drink will be provided.
simon The OpenMetrics exporter for FA is not accepting
simon The OpenMetrics exporter for FA is not accepting the hardcoded (unless you do some kind of jerryrig with relabeling) "target" parameter when receiving the GET request from Prometheus Operator. It is expecting the "endpoint" parameter instead. I made a small mistake opening a PR against the main repo with the simple substitution I made for internal purposes, but I believe a retro-compatible solution would be the best, one the accepts both parameter names. How would you prefer to handle it?
Hello all I have a Helm Template helper function
Hello all I have a Helm Template helper function that is creating a JSON object that I am using in a Helm chart to template out the px-pure-secret from my values file: ```{{/* Template flashblade secret */}} {{- define "sd_portworx.flashbladeSecret" -}} {{- with .Values.flashblade }} {{- printf "{\"FlashBlades\": [{\"MgmtEndPoint\": \"%s\", \"APIToken\": \"%s\", \"NFSEndPoint\": \"%s\"}]}" .managementEndpoint .apiToken .nfsEndpoint | b64enc }} {{- end }} {{- end }}``` I can really simply add a function to template out the flasharraySecret from values as well: ```flasharray: managementEndpoint: "my_array" apiToken: "my_token"``` Is there any way to have helm concat those two templates together and have it be a valid json?
