apps: update READMEs, remove --dry-run from deploy.sh

README.md

@@ -5,9 +5,10 @@ Kubernetes project infrastructure, managed by the kubernetes comunity via [wg-k8
 - `apps`: community-managed apps that run on the community-managed `aaa` cluster
     - `gcsweb`: instance of [gcsweb] at https://gcsweb.k8s.io - owned by [sig-testing]
     - `kubernetes-external-secrets`: instance of [kubernetes-external-secrets] - owned by [sig-testing]
-    - `node-perf-dash`: instance of [node-perf-dash] - owned by [sig-node] (TODO(https://github.com/kubernetes/k8s.io/issues/2150) migrate to apps/)
+    - `node-perf-dash`: instance of [node-perf-dash] - owned by [sig-node]
     - `sippy`: instance of [sippy] at https://sippy.k8s.io - owned by [sig-architecture] (on behalf of [wg-reliability])
     - `slack-infra`: instance of [slack-infra] including https://slack.k8s.io - owned by [sig-contributor-experience]
+    - `triageparty-release`: instance of [triage-party] - owned by [sig-release]
 - `audit`: scripts to export all relevant gcp resources, and the most recently-reviewed export
 - `cert-manager`: instance of [cert-manager] for the `aaa` cluster - owned by ???
 - `dns`: DNS for kubernetes.io and k8s.io
@@ -23,7 +24,6 @@ Kubernetes project infrastructure, managed by the kubernetes comunity via [wg-k8
 - `prow`: work-in-pogress instance of [prow] - owned by [sig-testing] (TODO(https://github.com/kubernetes/k8s.io/issues/2150) migrate to apps/)
 - `publishing-bot`: instance of [publishing-bot] - owned by [sig-release] (TODO(https://github.com/kubernetes/k8s.io/issues/2150) migrate to apps/)
 - `registry.k8s.io`: work-in-progress to support cross-cloud mirroring/hosting of containers and binaries
-- `triage-party/release-team`: instance of [triage-party] - owned by [sig-release] (TODO(https://github.com/kubernetes/k8s.io/issues/2150) migrate to apps/)
 
 TODO: are these actively in use or should they be retired?
 - `artifacts`
@@ -58,4 +58,4 @@ Please see https://git.k8s.io/community/wg-k8s-infra for more information
 [sig-scalability]: https://git.k8s.io/community/sig-scalability
 [sig-testing]: https://git.k8s.io/community/sig-testing
 [wg-k8s-infra]: https://git.k8s.io/community/wg-k8s-infra
-[wg-reliability]: https://git.k8s.io/community/wg-reliability
+[wg-reliability]: https://git.k8s.io/community/wg-reliability

apps/README.md

@@ -31,7 +31,7 @@ actually fits the apps we run today.
 - enforcement
     - OWNER constraints enforcemed by humans
     - no validation of yaml beyond yamllint
-    - `app:` convention enforcement by humands
+    - `app:` convention enforcement by humans
 - `*.yaml` can be more than k8s resources
     - consider a `resources/` subdir convention for all k8s resources
     - allows for config files etc. at app root
@@ -40,4 +40,4 @@ actually fits the apps we run today.
     - consider a custom label `k8s-infra-app:`; could do prefix but then need to decide on a DNS name
     - is this a convention worth enforcing? perhaps namespace is enough
 
-[running-in-community-clusters.md]: /running-in-community-clusters.md
+[running-in-community-clusters.md]: /running-in-community-clusters.md

apps/gcsweb/deploy.sh

@@ -47,4 +47,4 @@ fi
 
 # deploy kubernetes resources
 pushd "${SCRIPT_ROOT}" >/dev/null
-kubectl --context="${context}" --namespace="${namespace}" apply --dry-run=client -f .
+kubectl --context="${context}" --namespace="${namespace}" apply -f .

apps/kubernetes-external-secrets/deploy.sh

@@ -47,4 +47,4 @@ fi
 
 # deploy kubernetes resources
 pushd "${SCRIPT_ROOT}" >/dev/null
-kubectl --context="${context}" --namespace="${namespace}" apply --dry-run=client -f .
+kubectl --context="${context}" --namespace="${namespace}" apply -f .

apps/node-perf-dash/deploy.sh

@@ -47,4 +47,4 @@ fi
 
 # deploy kubernetes resources
 pushd "${SCRIPT_ROOT}" >/dev/null
-kubectl --context="${context}" --namespace="${namespace}" apply --dry-run=client -f .
+kubectl --context="${context}" --namespace="${namespace}" apply -f .

apps/sippy/deploy.sh

@@ -47,4 +47,4 @@ fi
 
 # deploy kubernetes resources
 pushd "${SCRIPT_ROOT}" >/dev/null
-kubectl --context="${context}" --namespace="${namespace}" apply --dry-run=client -f .
+kubectl --context="${context}" --namespace="${namespace}" apply -f .

apps/triageparty-release/deploy.sh

@@ -47,4 +47,4 @@ fi
 
 # deploy kubernetes resources
 pushd "${SCRIPT_ROOT}" >/dev/null
-kubectl --context="${context}" --namespace="${namespace}" apply --dry-run=client -f .
+kubectl --context="${context}" --namespace="${namespace}" apply -f .