| 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
Edit Prometheus server config map to scrape the kube-state-metrics being exposed
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
- 1qSdY4WIleWmdTbEbGs0WDo a rollout restart of the prometheus-server for the edited config map to take effect on the minikube cluster
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 monitoringcopied1