examples VS AKS

$ git clone https://github.com/dwmkerr/terraform-consul-cluster.git $ git clone https://github.com/splunk/splunk-aws-cloudformation.git $ git clone https://github.com/webdevops/Dockerfile.git $ git clone https://github.com/softprops/serverless-aws-rust-http.git $ git clone https://github.com/kubernetes/examples.git $ git clone https://github.com/prometheus-community/helm-charts.git

Then for the initators (k8s pods), just reference the builtin iSCSI CSI driver in your deployment's [volume config](https://github.com/kubernetes/examples/blob/master/volumes/iscsi/iscsi.yaml).

Reference: https://github.com/kubernetes/examples

I am setting up a kubernetes lab using one node only and learning to setup kubernetes nfs. I am following kubernetes nfs example step by step from the following link: https://github.com/kubernetes/examples/tree/master/staging/volumes/nfs

It doesn't seem like there are a lot of good open source k8's projects. One I could find was the kubernetes/examples repo.

Kubernetes has a decent example of using GlusterFS for Volume storage: fun documentation link

Now let's deploy something that will return some results. Kubernetes has multiple example applications available in a Github repo. We are going to deploy the Guestbook App with these commands:

Following this example Kubernetes iSCSI Example, I created a new raw LUN and deployed the below pod manifest:

Ah yep, you're right. Just found someone asking the same thing from two days ago in the Azure AKS GitHub https://github.com/Azure/AKS/issues/3689. It should definitely be pulling the Ubuntu 22.04 fips compliant image if it were available.

Just did a search not sure related to your problem https://github.com/Azure/AKS/issues/85

As I could gather additional information which indicates some problems with the Monitoring Agent (high cpu on ama pods, no metrics delivered during CPU pressure, ama pods emitting logs), I opened a ticket on GitHub (https://github.com/Azure/AKS/issues/3469). Hopefully this helps to resolve the issue.

While I'm glad I saw this here, it's not one of our primary support channels. In the future, you can also raise an issue in our GitHub repository or file a support request.

You're dependent on the cloud provider for security settings in a lot of cases and they don't always get it right (e.g. AKS still doesn't have Node Authorization enabled! https://github.com/Azure/AKS/issues/3004)

For ASK even v1.22 got out of support yesterday 04 of December. https://github.com/Azure/AKS/releases/tag/2022-11-27

The Workload Identity add-on for AKS is still in progress. AKS has a public roadmap where you can find this kind of information.

Reference: https://github.com/Azure/AKS

For Thanos receive and query components to be available outside the cluster and secured with TLS, we will need ingress-nginx and cert-manager. For ingress, deploy the Helm chart using the following command, to account for this issue with AKS clusters >1.23: