Kubernetes Service resources define networking abstractions that expose and connect applications running in Pods, enabling service discovery and load balancing. These include ClusterIP, NodePort, LoadBalancer, and ExternalName services, providing various levels of accessibility and networking capabilities.
Service Resources
The repository provides a robust collection of templates for Kubernetes service-related resources, including Service, Endpoints, Ingress, and IngressClass. These templates facilitate efficient network service management and traffic routing within clusters. Built on a flexible, facet-based design with dynamic variable population, they simplify the creation and configuration of service components while supporting diverse networking scenarios in Kubernetes environments.
Resources
| Resource | Description | Templates |
|---|---|---|
| Service | Exposes a set of pods as a network service, enabling stable access within the cluster. | v1 |
| Endpoints | Represents network endpoints that a Service routes traffic to. | v1 |
| Ingress | Manages external HTTP/S access to services, enabling traffic routing via rules. | v1 |
| IngressClass | Defines the controller responsible for handling Ingress resources in the cluster. | v1 |
Contributions
Permissions
Below are Configfacets Permissions overview and Kubernetes Organization structure.
Overview
A repository can be created under an Organization, Team, or User, with permissions inherited from the parent entity. An Admin role at the parent level grants admin privileges across all repositories and resources within it. In contrast, a Member role at the parent level, by default, has view access to private repositories and their resources but can be granted elevated permissions (such as Admin) for a specific repository. For more details, refer to the Configfacets Authorization documentation.
Kubernetes Organization
| Team | Description |
|---|---|
| Resources | The Kubernetes resources team will work on creating and managing configurations for Kubernetes resources, including workload resources, networking, storage and more. All resource repositories are organized under the Resources team hierarchy. |
| Maintainers | Kubernetes Maintainers team gets admin privileges all across Kubernetes organization. |
| Collaborators | Members of the Collaborators team receive Collaborator permissions, allowing them to edit resources in all repositories. |
If you'd like to contribute to the Service Resources repository, you can request Collaborator permission specific to this repository or join the Maintainers or Collaborators team.
Please reach out to us through our Discord community for permissions.
Releases
| Type | Description |
|---|---|
| Released | Versions in this state are finalized and cannot be modified by collaborators. They can be safely used as dependencies in repositories, ensuring stability for associated resources such as data, collections, configurations, services, and endpoints. |
| Under Development | These versions are still being actively worked on and may change without prior notice. Using them as dependencies should be done with caution, as resources within them, including configurations and services, are subject to updates. |
| Archived | Archived versions are no longer supported, and resource modifications are disabled. They cannot be newly added as dependencies, but any previously included versions will continue to function as they were.. |