I am testing the installation in a Cluster with Azure AKS. In a bash terminal I installed azure cli, got the aks credentials and runthe installer. He stops at the item below
*>>> Waiting for Operator to register custom resource definitions......**
Nodes:
NAME STATUS ROLES AGE VERSION
aks-agentpool-21009078-0 Ready agent 1d v1.11.3
aks-agentpool-21009078-1 Ready agent 1d v1.11.3
Thanks,
Ramon
------------------------ LOG ---------
root@LAPTOP:/temp/prometheus-kubernetes# ./deploy
Check for uncommitted changes
WARNING! You have uncommitted changes! Please commit your changes now, then press ENTER
M assets/alertmanager/alertmanager.yaml
M manifests/alertmanager/alertmanager.yaml
M manifests/grafana/grafana-datasources.cm.yaml
M manifests/grafana/grafana.de.yaml
M manifests/kube-state-metrics/kube-state-metrics-rbac.yaml
M manifests/kube-state-metrics/kube-state-metrics.de.yaml
M manifests/node-exporter/node-exporter.ds.yaml
M manifests/prometheus-operator/prometheus-operator-cluster-role-binding.yaml
M manifests/prometheus-operator/prometheus-operator.yaml
M manifests/prometheus/prometheus-k8s-rbac.yaml
M manifests/prometheus/prometheus-k8s-service-monitor-alertmanager.yaml
M manifests/prometheus/prometheus-k8s-service-monitor-kube-state-metrics.yaml
M manifests/prometheus/prometheus-k8s-service-monitor-node-exporter.yaml
M manifests/prometheus/prometheus-k8s-service-monitor-prometheus.yaml
M manifests/prometheus/prometheus-k8s.yaml
[ENTER]:
Enter desired namespace to deploy prometheus [monitoring]:
Creating monitoring namespace.
Error from server (AlreadyExists): namespaces "monitoring" already exists
1) AWS
2) GCP
3) Azure
4) Custom
Please select your cloud provider:3
Deploying on Azure
Are you deploying in Azure Container Engine (AKS)?
Y/N [N]: Y
Remove rules for self hosted clusters
Setting components version
Enter Prometheus Operator version [v0.23.1]:
Enter Prometheus version [v2.3.2]:
Enter Prometheus storage retention period in hours [168h]:
Enter Prometheus storage volume size [40Gi]:
Enter Prometheus memory request in Gi or Mi [1Gi]:
Do you want to use NodeSelector to assign monitoring components on dedicated nodes?
Y/N [N]: Y
Make sure you label the nodes correctly. The default label is: beta.kubernetes.io/monit=prometheus
Node label key [beta.kubernetes.io/monit]:
Node label value [prometheus]:
I am testing the installation in a Cluster with Azure AKS. In a bash terminal I installed azure cli, got the aks credentials and runthe installer. He stops at the item below
*>>> Waiting for Operator to register custom resource definitions......**
K8s: 1.11.3
Version Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:46:06Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-09T17:53:03Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Nodes: NAME STATUS ROLES AGE VERSION aks-agentpool-21009078-0 Ready agent 1d v1.11.3 aks-agentpool-21009078-1 Ready agent 1d v1.11.3
Thanks, Ramon
------------------------ LOG ---------
root@LAPTOP:/temp/prometheus-kubernetes# ./deploy Check for uncommitted changes
WARNING! You have uncommitted changes! Please commit your changes now, then press ENTER M assets/alertmanager/alertmanager.yaml M manifests/alertmanager/alertmanager.yaml M manifests/grafana/grafana-datasources.cm.yaml M manifests/grafana/grafana.de.yaml M manifests/kube-state-metrics/kube-state-metrics-rbac.yaml M manifests/kube-state-metrics/kube-state-metrics.de.yaml M manifests/node-exporter/node-exporter.ds.yaml M manifests/prometheus-operator/prometheus-operator-cluster-role-binding.yaml M manifests/prometheus-operator/prometheus-operator.yaml M manifests/prometheus/prometheus-k8s-rbac.yaml M manifests/prometheus/prometheus-k8s-service-monitor-alertmanager.yaml M manifests/prometheus/prometheus-k8s-service-monitor-kube-state-metrics.yaml M manifests/prometheus/prometheus-k8s-service-monitor-node-exporter.yaml M manifests/prometheus/prometheus-k8s-service-monitor-prometheus.yaml M manifests/prometheus/prometheus-k8s.yaml [ENTER]: Enter desired namespace to deploy prometheus [monitoring]: Creating monitoring namespace. Error from server (AlreadyExists): namespaces "monitoring" already exists 1) AWS 2) GCP 3) Azure 4) Custom Please select your cloud provider:3 Deploying on Azure Are you deploying in Azure Container Engine (AKS)? Y/N [N]: Y Remove rules for self hosted clusters
Setting components version Enter Prometheus Operator version [v0.23.1]:
Enter Prometheus version [v2.3.2]:
Enter Prometheus storage retention period in hours [168h]:
Enter Prometheus storage volume size [40Gi]:
Enter Prometheus memory request in Gi or Mi [1Gi]:
Enter Grafana version [5.2.2]:
Enter Alert Manager version [v0.15.1]:
Enter Node Exporter version [v0.16.0]:
Enter Kube State Metrics version [v1.3.1]:
Enter Prometheus external Url [http://127.0.0.1:9090]:
Enter Alertmanager external Url [http://127.0.0.1:9093]:
Do you want to use NodeSelector to assign monitoring components on dedicated nodes? Y/N [N]: Y
Make sure you label the nodes correctly. The default label is: beta.kubernetes.io/monit=prometheus Node label key [beta.kubernetes.io/monit]: Node label value [prometheus]:
Do you want to set up an SMTP relay? Y/N [N]: N
Do you want to set up slack alerts? Y/N [N]: N
Removing all the sed generated files
Deploying Prometheus Operator serviceaccount/prometheus-operator unchanged clusterrole.rbac.authorization.k8s.io/prometheus-operator unchanged clusterrolebinding.rbac.authorization.k8s.io/prometheus-operator unchanged service/prometheus-operator unchanged deployment.apps/prometheus-operator unchanged Waiting for Operator to register custom resource definitions.................................................................................................................... ................