diff --git a/docs/integrations.md b/docs/integrations.md
index 68f44df06..e17463cb1 100644
--- a/docs/integrations.md
+++ b/docs/integrations.md
@@ -147,10 +147,6 @@ The plugin configuration structure is defined [here](https://pkg.go.dev/github.c
 
 This is a little tricky since you have to look at the source code of the plugin to figure out the `ID`. In the case of Spark, for example, the value of `ID` is used [here](https://github.com/flyteorg/flyteplugins/blob/v0.5.25/go/tasks/plugins/k8s/spark/spark.go#L424) here, defined as [spark](https://github.com/flyteorg/flyteplugins/blob/v0.5.25/go/tasks/plugins/k8s/spark/spark.go#L41).
 
-**Enabling a Specific Backend Plugin in Your Own Kustomize Generator**
-
-Flyte uses Kustomize to generate the the deployment configuration which can be leveraged to [kustomize your own deployment](https://github.com/flyteorg/flyte/tree/master/kustomize).
-
 ::::
 
 ## SDKs for Writing Tasks and Workflows
diff --git a/examples/productionizing/productionizing/use_secrets.py b/examples/productionizing/productionizing/use_secrets.py
index 1c7f8d78a..e4006e2b9 100644
--- a/examples/productionizing/productionizing/use_secrets.py
+++ b/examples/productionizing/productionizing/use_secrets.py
@@ -352,9 +352,6 @@ def my_secret_workflow() -> Tuple[str, str, str, str, str]:
 # - [AWS Secret Manager](https://docs.aws.amazon.com/secretsmanager/latest/userguide/create_secret.html): `flyte-pod-webhook` will add the AWS Secret Manager sidecar container to a task Pod which will mount the secret.
 # - [Vault Agent Injector](https://developer.hashicorp.com/vault/tutorials/getting-started/getting-started-first-secret#write-a-secret) : `flyte-pod-webhook` will annotate the task Pod with the respective Vault annotations that trigger an existing Vault Agent Injector to retrieve the specified secret Key from a vault path defined as secret Group.
 #
-# You can configure the additional secret manager by defining `secretManagerType` to be either 'K8s', 'AWS' or 'Vault' in
-# the [core config](https://github.com/flyteorg/flyte/blob/master/kustomize/base/single_cluster/headless/config/propeller/core.yaml#L34) of the Flytepropeller.
-#
 # When using the K8s secret manager plugin, which is enabled by default, the secrets need to be available in the same namespace as the task execution
 # (for example `flytesnacks-development`). K8s secrets can be mounted as either files or injected as environment variables into the task pod,
 # so if you need to make larger files available to the task, then this might be the better option.