Skip to content
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.

Sign up for GitHub

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

DNM: Add metrics-server to the default installation #19

Closed
wants to merge 1 commit into from
Closed

DNM: Add metrics-server to the default installation #19

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 11 additions & 13 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ config/

You will need to download some files from your Kubernetes masters and put them in their respective directories in ./config

If you used kubeadm, more information is here:
If you used kubeadm, more information is here:

https://kubernetes.io/docs/setup/best-practices/certificates/#where-certificates-are-stored

Expand All @@ -93,7 +93,7 @@ Read any notes that are printed after successful installation, and follow any ad

## Post-install

Some of the objects installed require DNS to work in order for them to start up and work correctly. After running the installer script, query your nginx service to discover the DNS address of your AWS Elastic Load Balancer (ELB) and add that as a wildcard for the domain, since this is where all of our web traffic will go.
Some of the objects installed require DNS to work in order for them to start up and work correctly. After running the installer script, query your nginx service to discover the DNS address of your AWS Elastic Load Balancer (ELB) and add that as a wildcard for the domain, since this is where all of our web traffic will go.

Find the service with:

Expand All @@ -105,15 +105,15 @@ md-nginx-ingress-controller LoadBalancer 10.96.228.202 somelongdns.us

Then, for example, in your DNS create a CNAME for `*.foo.example.com` to `somelongdns.us-east-1.elb.amazonaws.com`

This will allow traffic to reach the cluster and complete the installation process. At this point, certificates should begin to solve via `cert-manager`. Wait a bit and then check if you can reach
This will allow traffic to reach the cluster and complete the installation process. At this point, certificates should begin to solve via `cert-manager`. Wait a bit and then check if you can reach

## Troubleshooting

Hopefully the installer will exit with a helpful error. If not, the line it exits on is going to be your best clue as to where to look to debug further. Ensure helmreleases are deployed correctly by running
Hopefully the installer will exit with a helpful error. If not, the line it exits on is going to be your best clue as to where to look to debug further. Ensure helmreleases are deployed correctly by running

`helm list --all-namespaces` which should show `deployed` for all services.
`helm list --all-namespaces` which should show `deployed` for all services.

If any of the components appear to be missing, you can describe the helmrelease to try to see what went wrong with its installation. Failing that, you can look at the logs of pods in the individual namespaces the installer creates for each helmrelease.
If any of the components appear to be missing, you can describe the helmrelease to try to see what went wrong with its installation. Failing that, you can look at the logs of pods in the individual namespaces the installer creates for each helmrelease.

If all else fails feel free to open an issue and we will try to help you!

Expand Down Expand Up @@ -187,10 +187,8 @@ If all else fails feel free to open an issue and we will try to help you!
| `etcd.ca.crt` | The Kubernetes masters' CA certificate | |
| `etcd.healthcheckClient.crt` | The CA certificate for the `etcd` healthcheck client (also comes from Kubernetes masters) | |
| `etcd.healthcheckClient.key` | The private key for the `etcd` healthcheck client (also comes from Kubernetes masters) | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| `metricsServer.create` | Whether or not to install `metrics-server` | true |
| `metricsServer.version` | Chart version | [2.11.1](https://hub.helm.sh/charts/stable/metrics-server/2.11.1 ) |
| `metricsServer.pspEnabled` | Whether or not to enable Pod Security Policy | true |
| `metricsServer.hostNetworkEnabled` | Whether or not to enable host networking | true |
| `metricsServer.args` | Command args to pass through to `metrics-server` | [] |
26 changes: 26 additions & 0 deletions templates/metrics-server.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
{{- if .Values.metricsServer.create }}

apiVersion: helm.fluxcd.io/v1
kind: HelmRelease
metadata:
name: metrics-server
namespace: kube-system
spec:
releaseName: metrics-server
chart:
repository: https://kubernetes-charts.storage.googleapis.com/
name: metrics-server
version: {{ .Values.metricsServer.version }}
values:
rbac:
pspEnabled: {{ .Values.metricsServer.pspEnabled }}
hostNetwork:
enabled: {{ .Values.metricsServer.hostNetworkEnabled }}
{{- with .Values.metricsServer.args}}
args:
{{- toYaml . | nindent 6}}
{{- else }}
  args: []
{{- end }}

{{- end }}
7 changes: 7 additions & 0 deletions values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -148,3 +148,10 @@ etcd:
{}
# crt: "set via CLI"
# key: "set via in CLI"

metricsServer:
create: true
version: 2.11.1
pspEnabled: true
hostNetworkEnabled: true
args: []