wg-serverless VS AKS

Check out CNCF Projects. Contributing to some of these open source projects is a great way to gain skills and land a job.

would indicate if your cluster could retrieve content from cncf.io or if cncf.io is up.

This solution builds upon well-established Cloud Native Computing Foundation (CNCF) open source projects like Thanos and Prometheus,together with a new managed services, Azure Managed Grafana, recently released in public preview. It allows for ephemeral clusters to still have updated metrics without the 2-hours local storage of metrics in the classic deployment of Thanos sidecar to Prometheus.

Not ELI5 but see https://github.com/cncf/wg-serverless/tree/master/whitepaper...

Some people go monolithic app but best practice is usually one function per route.

Traditional servers come with management overhead (e.g. defining/managing/monitoring scaling) and by using Serverless servers you avoid that overhead and optimize for good engineers which are almost always your bigger cost center.

github.com/cncf/wg-serverless/blob/master/w..

As stated in a white paper by the CNCF serverless working group, there are two primary serverless personas:

The CloudEvents specification is under the CNCF Serverless working group since 2018. The spec's purpose is describing event data in a common way. This is useful in many scenarios, for example, routing events to the appropriate subscribers depending on the type of the event. Since applications can use a lot of different transports to send and receive events, the CloudEvents spec is protocol-agnostic so it defines protocol bindings in order for the metadata to be correctly mapped for HTTP, AMQP, Kafka, etc.

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: