| agent: | Auto Exec |
What is an "Expert"? How do we create our own expert?
Add credentials for various integrations
Managing workspaces and access control
DagKnows Architecture Overview
Setting up SSO via Azure AD for Dagknows
Enable "Auto Exec" and "Send Execution Result to LLM" in "Adjust Settings" if desired
(Optionally) Add ubuntu user to docker group and refresh group membership
Deployment of an EKS Cluster with Worker Nodes in AWS
Adding, Deleting, Listing DagKnows Proxy credentials or key-value pairs
Comprehensive AWS Security and Compliance Evaluation Workflow (SOC2 Super Runbook)
AWS EKS Version Update 1.29 to 1.30 via terraform
Instruction to allow WinRM connection
MSP Usecase: User Onboarding Azure + M365
Post a message to a Slack channel
How to debug a kafka cluster and kafka topics?
Open VPN Troubleshooting (Powershell)
Execute a simple task on the proxy
Assign the proxy role to a user
Create roles to access credentials in proxy
Install OpenVPN client on Windows laptop
Setup Kubernetes kubectl and Minikube on Ubuntu 22.04 LTS
Install Prometheus and Grafana on the minikube cluster on EC2 instance in the monitoring namespace
update the EKS versions in different clusters
AI agent session 2024-09-12T09:36:14-07:00 by Sarang Dharmapurikar
Parse EDN content and give a JSON out
Check whether a user is there on Azure AD and if the user account status is enabled
Get the input parameters of a Jenkins pipeline
Install Prometheus and Grafana on the minikube cluster on EC2 instance in the monitoring namespace
- 1yDWk0ZDuvWH8lxtNpqIeInstall helm on minikube cluster on EC2 Instance
1
Install helm on minikube cluster on EC2 Instance
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.inputsoutputs# To install helm curl -fsSL -o get_helm.sh https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 chmod 700 get_helm.sh ./get_helm.shcopied1 - 2gRju36utdmyXP0gfANM7Create a namespace called monitoring on the minikube cluster on the EC2 instance
2
Create a namespace called monitoring on the minikube cluster on the EC2 instance
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.inputsoutputs# Create a namespace monitoring kubectl create namespace monitoringcopied2 - 3H0KELyb9ftK7koD19lklInstall Prometheus on minikube cluster
3
Install Prometheus on minikube cluster
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.inputsoutputs3- 3.1LuACU3cvcT8bEzFABmbsAdd a helm repo for prometheus on the minikube cluster
3.1
Add a helm repo for prometheus on the minikube cluster
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.inputsoutputs# To add helm chart for prometheus helm repo add prometheus-community https://prometheus-community.github.io/helm-chartscopied3.1 - 3.2ewYpwdG0k2sjO5Zff0KxInstall Prometheus on minikube cluster in the monitoring namespace
3.2
Install Prometheus on minikube cluster in the monitoring namespace
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.inputsoutputs# Installing prometheus in monitoring namespace helm install prometheus prometheus-community/prometheus --namespace monitoringcopied3.2 - 3.3N9WxhE3DSJZe74rDPmt0To expose prometheus service (so it can be accessed outside the cluster)
3.3
To expose prometheus service (so it can be accessed outside the cluster)
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.inputsoutputs# To expose prometheus service (would change type from cluster IP to node port and create a new service) kubectl expose service prometheus-server --namespace=monitoring --type=NodePort --target-port=9090 --name=prometheus-server-extcopied3.3
- 4g6l9VDWcylbzhdVsim5ZInstall Grafana on minikube cluster
4
Install Grafana on minikube cluster
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.inputsoutputs4- 4.1AUz8kfhhcvdPVgyQqzEZAdd a helm repo for grafana on the minikube cluster
4.1
Add a helm repo for grafana on the minikube cluster
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.inputsoutputs# Add helm repo for grafana helm repo add grafana https://grafana.github.io/helm-chartscopied4.1 - 4.2npgy3GBCkP6T3VWpvAGnInstall Grafana on minikube cluster in the monitoring namespace with persistence enabled
4.2
Install Grafana on minikube cluster in the monitoring namespace with persistence enabled
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.(Need to test out the persistence enabled flags with execution)
inputsoutputs# To install the helm repo in the monitoring namespace with persistence enabled helm install grafana grafana/grafana --namespace monitoring --set persistence.enabled=true,persistence.size=5Gi,persistence.storageClassName=standardcopied4.2 - 4.3QJA6fVbqicb1kqjHnTQKFetch the user name (admin) and password for grafana from the install information
4.3
Fetch the user name (admin) and password for grafana from the install information
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.Usually the secret is accessed using
# Get your 'admin' user password by running:
kubectl get secret --namespace monitoring grafana -o jsonpath="{.data.admin-password}" | base64 --decode ; echo
inputsoutputs# Get your 'admin' user password by running: kubectl get secret --namespace monitoring grafana -o jsonpath="{.data.admin-password}" | base64 --decode ; echocopied4.3 - 4.4nPMB9IReck0lcHPAIJxUTo expose grafana service so it can be accessed outside the cluster)
4.4
To expose grafana service so it can be accessed outside the cluster)
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.inputsoutputs# To Expose Grafana service kubectl expose service grafana --type=NodePort --target-port=3000 --name=grafana-ext -n monitoringcopied4.4
- 5EetlRPRVAoLtSkS6lKpvSet prometheus as a data source for your grafana service in the minikube cluster
5
Set prometheus as a data source for your grafana service in the minikube cluster
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.# Add prometheus as a data source for your grafana
http://<minikube_ip>:<prom_service_node_port>
# For example
http://192.168.49.2:31000
# Get node ports by running
kubectl get svc -A
Go to Grafana > Home > Connections > Add New Connections
inputsoutputs# Add prometheus as a data source for your grafana http://<minikube_ip>:<prom_service_node_port>copied5 - 6H6YGoxgjsICP1TBH4Gu3Expose prometheus-kube-state-metrics service in monitoring namespace to access the kube-state-metrics outside the cluster
6
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.inputsoutputs# Expose prometheus-kube-state-metrics service in monitoring namespace kubectl expose service prometheus-kube-state-metrics --type=NodePort --target-port=8080 --name=prometheus-kube-state-metrics-ext -n monitoringcopied6 - 7OPAY4sEBtysYLa9bmlUBEdit Prometheus server config map to scrape the kube-state-metrics being exposed
7
Edit Prometheus server config map to scrape the kube-state-metrics being exposed
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.kubectl get cm
kubectl edit cm <config_map_name> -n monitoring
# For Example
kubectl edit cm prometheus-server -n monitoring
# Add a scraping job in prometheus-server cm under scrape configs
- job_name: state_metrics
static_configs:
- targets:
- prometheus-kube-state-metrics.monitoring.svc.cluster.local:8080
After doing a rollout restart of the prometheus-server we can access the kube-state-metrics from the grafana/prometheus
inputsoutputs# Can be skipped if doing step 9 kubectl get cm kubectl edit cm <config_map_name> -n monitoring # For Example kubectl edit cm prometheus-server -n monitoring # Add a scraping job in prometheus-server cm under scrape configs - job_name: state_metrics static_configs: - targets: - prometheus-kube-state-metrics.monitoring.svc.cluster.local:8080copied7- 7.1qSdY4WIleWmdTbEbGs0WDo a rollout restart of the prometheus-server for the edited config map to take effect on the minikube cluster
7.1
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.After this we can access the kube-state-metrics from the grafana/prometheus
inputsoutputs# after editing the config map do a rollout restart if needed kubectl rollout restart deployment prometheus-server -n monitoringcopied7.1