Skip to content

SAP/nginx-ingress-controller-cop

Folders and files

NameName
Last commit message
Last commit date

Latest commit

dffd3ff · Dec 30, 2024
Dec 18, 2024
Dec 4, 2024
Sep 5, 2023
Jun 13, 2023
Dec 4, 2024
Dec 30, 2024
Dec 19, 2024
Sep 5, 2023
Dec 4, 2024
Dec 4, 2024
Dec 4, 2024
Sep 5, 2023
Oct 16, 2023
Sep 5, 2023
Jun 13, 2023
Aug 28, 2024
Sep 5, 2023
Aug 27, 2024
Dec 4, 2024
Dec 23, 2024
Dec 23, 2024
Dec 4, 2024
Mar 25, 2024

Repository files navigation

Nginx Ingress Controller Component Operator

REUSE status

About this project

Component Operator for https://github.com/kubernetes/ingress-nginx.

After installing this component operator into a Kubernetes cluster, nginx ingress controllers may be installed by deploying

apiVersion: operator.kyma-project.io/v1alpha1
kind: NginxIngressController
metadata:
  name: nginx-ingress-controller
# spec:
  # optional spec attributes

In spec, all values of the upstream Helm chart are allowed. Caveats:

  • the component operator does not perform any validation, it just passes the provided spec as values to the helm chart
  • the supported/allowed spec format might change, when the included upstream chart changes
  • deploying multiple NginxIngressController resources may or may not work, depending on the supplied values, i.e. it may fail if the configuration leads to deployment of clashing singleton resources such as custom resource definitions, webhook definitions, ...

In addition, the following attributes can be supplied in spec:

  • namespace: target namespace for the deployed ingress controller (if not specified, the namespace of the owning NginxIngressController resource will be used)
  • name: target name for the deployed ingress controller (if not specified, generated resources will be prefixed with the name of the owning NginxIngressController resource)
  • additionalResources: array of additional resource manifests that will be deployed along with the ingress controller.

Support, Feedback, Contributing

This project is open to feature requests/suggestions, bug reports etc. via GitHub issues. Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines.

Code of Conduct

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its Code of Conduct at all times.

Licensing

Copyright 2024 SAP SE or an SAP affiliate company and nginx-ingress-controller-cop contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.