Skip to content

Instantly share code, notes, and snippets.

@rynowak
Created May 24, 2024 20:14
Show Gist options
  • Save rynowak/e795d6c4ea1f42c3157643cea3002e44 to your computer and use it in GitHub Desktop.
Save rynowak/e795d6c4ea1f42c3157643cea3002e44 to your computer and use it in GitHub Desktop.
WG-Infructure Lifecycle Charter

From Thomas in GH Issue: To deploy applications successfully, there are efforts that often go hand in hand with infrastructure provisioning and deployment. As we see more projects from the infrastructure space in our TAG and identified (at a poll at KubeCon) that we should get more active in this area, there should be first investigations if it makes sense to build a working group for such topics, if there are enough interested people in this and what the potential scope of the WG could be.

As the Cloud space and CloudNative has gotten more mature, there are increasingly complex hybrid environments that do not run solely within the cloud. This can be a mixture of on-prem physical infrastructure, public/private cloud, and Edge/IOT. Various end-users are adopting CloudNative practices to modernize their stack with different levels of maturity.

Modern cloud-native applications depend on a variety of software infrastructure such as Kubernetes clusters, virtual networks, database servers, API gateways, or machine-learning models. Infrastructure may be software hosted inside a Kubernetes cluster, as services in public, private, or hybrid clouds, or on physical devices at the edge or in an on-premise datacenter.

The job for end-users that manage infrastructure has become increasingly more complex as they work to meet organizational requirements for cost, security, and reliability of operations. The complexity if

End users are increasingly using cloud-native practices to manage their infrastrcuture. Every user benefits from the abil

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment