Fix migrating nginxinc to nginx (#520)

AlexFenlon · web-flow · commit eff5d7f1960c · 2025-07-01T16:27:31.000+01:00
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -4,7 +4,7 @@ Describe the use case and detail of the change. If this PR addresses an issue on
 ### Checklist
 Before creating a PR, run through this checklist and mark each as complete.
 
-- [ ] I have read the [CONTRIBUTING](https://github.com/nginxinc/nginx-ingress-operator/blob/main/CONTRIBUTING.md) doc
+- [ ] I have read the [CONTRIBUTING](https://github.com/nginx/nginx-ingress-operator/blob/main/CONTRIBUTING.md) doc
 - [ ] I have added tests that prove my fix is effective or that my feature works
 - [ ] I have checked that all unit tests pass after adding my changes
 - [ ] I have updated necessary documentation
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
@@ -79,7 +79,7 @@ jobs:
         with:
           images: |
             nginx/nginx-ingress-operator
-            ghcr.io/nginxinc/nginx-ingress-operator
+            ghcr.io/nginx/nginx-ingress-operator
             quay.io/nginx/nginx-ingress-operator
           tags: |
             type=edge
diff --git a/.github/workflows/dependency-review.yml b/.github/workflows/dependency-review.yml
@@ -24,4 +24,4 @@ jobs:
       - name: "Dependency Review"
         uses: actions/dependency-review-action@da24556b548a50705dd671f47852072ea4c105d9 # v4.7.1
         with:
-          config-file: "nginxinc/k8s-common/dependency-review-config.yml@main"
+          config-file: "nginx/k8s-common/dependency-review-config.yml@main"
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,3 +1,3 @@
 # Changelog
 
-An automatically generated list of changes can be found on the [GitHub Releases page](https://github.com/nginxinc/nginx-ingress-helm-operator/releases).
+An automatically generated list of changes can be found on the [GitHub Releases page](https://github.com/nginx/nginx-ingress-helm-operator/releases).
diff --git a/CODEOWNERS b/CODEOWNERS
@@ -1 +1 @@
-* @nginxinc/kic
+* @nginx/kic
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -17,17 +17,17 @@ The following is a set of guidelines for contributing to the NGINX Ingress Opera
 
 ## Ask a Question
 
-To ask a question please use [Github Discussions](https://github.com/nginxinc/kubernetes-ingress/discussions).
+To ask a question please use [Github Discussions](https://github.com/nginx/kubernetes-ingress/discussions).
 
-You can also join our [Community Slack](https://community.nginx.org/joinslack) which has a wider NGINX audience.
+You can also get help through the [NGINX Community Forum](https://community.nginx.org/).
 
 Please reserve GitHub issues for feature requests and bugs rather than general questions.
 
 ## Getting Started
 
 Follow our [Installation Guide](docs/installation.md) to get the NGINX Ingress Operator up and running.
 
-Read the [documentation](https://github.com/nginxinc/nginx-ingress-helm-operator/tree/main/docs) .
+Read the [documentation](https://github.com/nginx/nginx-ingress-helm-operator/tree/main/docs) .
 
 ### Project Structure
 
diff --git a/PROJECT b/PROJECT
@@ -6,7 +6,7 @@ plugins:
   scorecard.sdk.operatorframework.io/v2: {}
   sdk.x-openshift.io/v1: {}
 projectName: nginx-ingress-operator
-repo: github.com/nginxinc/nginx-ingress-helm-operator
+repo: github.com/nginx/nginx-ingress-helm-operator
 resources:
 - api:
     crdVersion: v1
diff --git a/README.md b/README.md
@@ -1,11 +1,11 @@
-[![Continuous Integration](https://github.com/nginxinc/nginx-ingress-helm-operator/workflows/Continuous%20Integration/badge.svg)](https://github.com/nginxinc/nginx-ingress-helm-operator/actions)
-[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/nginxinc/nginx-ingress-helm-operator/badge)](https://api.securityscorecards.dev/projects/github.com/nginxinc/nginx-ingress-helm-operator)
+[![Continuous Integration](https://github.com/nginx/nginx-ingress-helm-operator/workflows/Continuous%20Integration/badge.svg)](https://github.com/nginx/nginx-ingress-helm-operator/actions)
+[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/nginx/nginx-ingress-helm-operator/badge)](https://api.securityscorecards.dev/projects/github.com/nginx/nginx-ingress-helm-operator)
 [![Project Status: Active – The project has reached a stable, usable state and is being actively developed.](https://www.repostatus.org/badges/latest/active.svg)](https://www.repostatus.org/#active)
 ![Commercial Support](https://badgen.net/badge/support/commercial/green?icon=awesome)
 
 # NGINX Ingress Operator
 
-The NGINX Ingress Operator is a Kubernetes/OpenShift component which deploys and manages one or more [NGINX/NGINX Plus Ingress Controllers](https://github.com/nginxinc/kubernetes-ingress) which in turn handle Ingress traffic for applications running in a cluster.
+The NGINX Ingress Operator is a Kubernetes/OpenShift component which deploys and manages one or more [NGINX/NGINX Plus Ingress Controllers](https://github.com/nginx/kubernetes-ingress) which in turn handle Ingress traffic for applications running in a cluster.
 
 Learn more about operators in the [Kubernetes Documentation](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/).
 
@@ -46,11 +46,11 @@ Note: The NGINX Ingress Operator works only for NGINX Ingress Controller version
 
 1. Install the NGINX Ingress Operator. See [docs](./docs/installation.md).
    <br> NOTE: To use TransportServers as part of your NGINX Ingress Controller configuration, a GlobalConfiguration resource must be created _before_ starting the Operator - [see the notes](./examples/deployment-oss-min/README.md#TransportServers)
-2. Creating the default-server-secret.yaml is optional and it is recommended that users provide their own certificate. An example yaml for this can be found in the [examples folder](https://github.com/nginxinc/nginx-ingress-helm-operator/blob/main/examples/default-server-secret.yaml)
+2. Creating the default-server-secret.yaml is optional and it is recommended that users provide their own certificate. An example yaml for this can be found in the [examples folder](https://github.com/nginx/nginx-ingress-helm-operator/blob/main/examples/default-server-secret.yaml)
 3. (If using OpenShift) Create the scc resource on the cluster by applying the scc.yaml file found in the `resources` folder of this repo:
 
    ```shell
-   kubectl apply -f https://raw.githubusercontent.com/nginxinc/nginx-ingress-helm-operator/main/resources/scc.yaml
+   kubectl apply -f https://raw.githubusercontent.com/nginx/nginx-ingress-helm-operator/main/resources/scc.yaml
    ```
 
 4. Deploy a new NGINX Ingress Controller using the [NginxIngress](./config/samples/charts_v1alpha1_nginxingress.yaml) Custom Resource:
@@ -76,9 +76,9 @@ See [upgrade docs](./docs/upgrades.md)
 
 ## NGINX Ingress Operator Releases
 
-We publish NGINX Ingress Operator releases on GitHub. See our [releases page](https://github.com/nginxinc/nginx-ingress-helm-operator/releases).
+We publish NGINX Ingress Operator releases on GitHub. See our [releases page](https://github.com/nginx/nginx-ingress-helm-operator/releases).
 
-The latest stable release is [3.1.0](https://github.com/nginxinc/nginx-ingress-helm-operator/releases/tag/v3.1.0). For production use, we recommend that you choose the latest stable release.
+The latest stable release is [3.1.0](https://github.com/nginx/nginx-ingress-helm-operator/releases/tag/v3.1.0). For production use, we recommend that you choose the latest stable release.
 
 ## Development
 
diff --git a/bundle/manifests/nginx-ingress-operator.clusterserviceversion.yaml b/bundle/manifests/nginx-ingress-operator.clusterserviceversion.yaml
@@ -240,7 +240,7 @@ metadata:
     operatorframework.io/suggested-namespace: nginx-ingress
     operators.operatorframework.io/builder: operator-sdk-v1.40.0
     operators.operatorframework.io/project_layout: helm.sdk.operatorframework.io/v1
-    repository: https://github.com/nginxinc/nginx-ingress-helm-operator
+    repository: https://github.com/nginx/nginx-ingress-helm-operator
     support: NGINX Inc.
   labels:
     operatorframework.io/arch.amd64: supported
@@ -519,7 +519,7 @@ spec:
   - openshift
   links:
   - name: Nginx Ingress Operator
-    url: https://github.com/nginxinc/nginx-ingress-helm-operator
+    url: https://github.com/nginx/nginx-ingress-helm-operator
   maintainers:
   - email: kubernetes@nginx.com
     name: NGINX Inc
diff --git a/config/manifests/bases/nginx-ingress-operator.clusterserviceversion.yaml b/config/manifests/bases/nginx-ingress-operator.clusterserviceversion.yaml
@@ -21,7 +21,7 @@ metadata:
     features.operators.openshift.io/token-auth-azure: "false"
     features.operators.openshift.io/token-auth-gcp: "false"
     operatorframework.io/suggested-namespace: nginx-ingress
-    repository: https://github.com/nginxinc/nginx-ingress-helm-operator
+    repository: https://github.com/nginx/nginx-ingress-helm-operator
     support: NGINX Inc.
   labels:
     operatorframework.io/arch.amd64: supported
@@ -283,7 +283,7 @@ spec:
   - openshift
   links:
   - name: Nginx Ingress Operator
-    url: https://github.com/nginxinc/nginx-ingress-helm-operator
+    url: https://github.com/nginx/nginx-ingress-helm-operator
   maintainers:
   - email: kubernetes@nginx.com
     name: NGINX Inc
diff --git a/docs/manual-installation.md b/docs/manual-installation.md
@@ -7,7 +7,7 @@ This will deploy the operator in the `nginx-ingress-operator-system` namespace.
    1. Clone the `nginx-ingress-operator` repo:
 
    ```shell
-   git clone https://github.com/nginxinc/nginx-ingress-helm-operator/ --branch v3.1.0
+   git clone https://github.com/nginx/nginx-ingress-helm-operator/ --branch v3.1.0
    cd nginx-ingress-helm-operator/
    ```
 
@@ -30,11 +30,11 @@ This will deploy the operator in the `nginx-ingress-operator-system` namespace.
 
 In order to deploy NGINX Ingress Controller instances into OpenShift environments, a new SCC is required to be created on the cluster which will be used to bind the specific required capabilities to the NGINX Ingress service account(s). To do so for NIC deployments, please run the following command (assuming you are logged in with administrator access to the cluster):
 
-`kubectl apply -f https://raw.githubusercontent.com/nginxinc/nginx-ingress-helm-operator/v3.1.0/resources/scc.yaml`
+`kubectl apply -f https://raw.githubusercontent.com/nginx/nginx-ingress-helm-operator/v3.1.0/resources/scc.yaml`
 
 Alternatively, to create an SCC for NIC daemonsets, please run this command:
 
-`kubectl apply -f https://raw.githubusercontent.com/nginxinc/nginx-ingress-helm-operator/v3.1.0/resources/scc-daemonset.yaml`
+`kubectl apply -f https://raw.githubusercontent.com/nginx/nginx-ingress-helm-operator/v3.1.0/resources/scc-daemonset.yaml`
 
 You can now deploy the NGINX Ingress Controller instances.
 
diff --git a/docs/openshift-installation.md b/docs/openshift-installation.md
@@ -23,10 +23,10 @@ Additional steps:
 
 In order to deploy NGINX Ingress Controller instances into OpenShift environments, a new SCC is required to be created on the cluster which will be used to bind the specific required capabilities to the NGINX Ingress service account(s). To do so for NIC deployments, please run the following command (assuming you are logged in with administrator access to the cluster):
 
-`kubectl apply -f https://raw.githubusercontent.com/nginxinc/nginx-ingress-helm-operator/v3.1.0/resources/scc.yaml`
+`kubectl apply -f https://raw.githubusercontent.com/nginx/nginx-ingress-helm-operator/v3.1.0/resources/scc.yaml`
 
 Alternatively, to create an SCC for NIC daemonsets, please run this command:
 
-`kubectl apply -f https://raw.githubusercontent.com/nginxinc/nginx-ingress-helm-operator/v3.1.0/resources/scc-daemonset.yaml`
+`kubectl apply -f https://raw.githubusercontent.com/nginx/nginx-ingress-helm-operator/v3.1.0/resources/scc-daemonset.yaml`
 
 You can now deploy the NGINX Ingress Controller instances.
diff --git a/docs/upgrades.md b/docs/upgrades.md
@@ -44,7 +44,7 @@ Deploy the operator following the steps outlined in [manual installation doc](./
 
 Uninstall the existing operator deployment:
 
-1. Checkout the previous version of the nginx-ingress-operator [0.5.1](https://github.com/nginxinc/nginx-ingress-helm-operator/releases/tag/v0.5.1).
+1. Checkout the previous version of the nginx-ingress-operator [0.5.1](https://github.com/nginx /nginx-ingress-helm-operator/releases/tag/v0.5.1).
 2. Uninstall the resources by running the following command:
 
     ```shell

Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,3 @@`
`1`	`1`	`# Changelog`
`2`	`2`
`3`		`-An automatically generated list of changes can be found on the [GitHub Releases page](https://github.com/nginxinc/nginx-ingress-helm-operator/releases).`
	`3`	`+An automatically generated list of changes can be found on the [GitHub Releases page](https://github.com/nginx/nginx-ingress-helm-operator/releases).`