We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Most of our kubernetes specifications are of kind Deployment or Service. Therefore the containers are actually in the deployment yamls.
For example:
kind: Deployment metadata: name: heapster namespace: kube-system spec: replicas: 1 template: metadata: labels: task: monitoring k8s-app: heapster spec: containers: - name: heapster resources: limits: cpu: 100m memory: 100Mi requests: cpu: 100m memory: 100Mi image: gcr.io/google_containers/heapster-amd64:v1.3.0-beta.1 imagePullPolicy: IfNotPresent command: - /heapster - --source=kubernetes:https://kubernetes.default - --sink=influxdb:http://monitoring-influxdb:8086```
The text was updated successfully, but these errors were encountered:
This will be next to be implemented for sure. Thanks for the feedback.
Sorry, something went wrong.
Ingress is high up on my list as well.. thanks for the tool @viglesiasce!
Ingress
No branches or pull requests
Most of our kubernetes specifications are of kind Deployment or Service. Therefore the containers are actually in the deployment yamls.
For example:
The text was updated successfully, but these errors were encountered: