diff --git a/RELEASE.md b/RELEASE.md index b133d5e12e..d4c21f95da 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -15,4 +15,4 @@ It will create a tag and then publish all deployment manifest in github release and will create a discussion thread in github release 1. Kick off a run of the functional tests in https://github.com/unionai/genesis-device/actions/workflows/update_cluster_and_run_tests.yml 1. Close the milestone -1. Ping #core (slack channel) to: Send announcements about the milestone with the contents of the CHANGELOG to all social channels.. +1. Ping #core ([slack](https://slack.flyte.org/) channel) to send announcements about the milestone with the contents of the CHANGELOG to all social channels. diff --git a/rsts/deployment/cluster_config/general.rst b/rsts/deployment/cluster_config/general.rst index d71dafe994..f00d87eb0e 100644 --- a/rsts/deployment/cluster_config/general.rst +++ b/rsts/deployment/cluster_config/general.rst @@ -240,7 +240,19 @@ Using Default K8s PodTemplates To initialize a default PodTemplate in Flyte: -#. **Set the 'default-pod-template-name' in FlytePropeller:** This `option `__ initializes a K8s informer internally to track system PodTemplate updates (creates, updates, etc) so that FlytePropeller is aware of the latest PodTemplate definitions in the K8s environment. +#. **Set the 'default-pod-template-name' in FlytePropeller:** This `option `__ initializes a K8s informer internally to track system PodTemplate updates (creates, updates, etc) so that FlytePropeller is `aware `__ of the latest PodTemplate definitions in the K8s environment. You can find this setting in `FlytePropeller `__ config map, which is not set by default. + +An example configuration is: + +.. code-block:: yaml + + plugins: + k8s: + co-pilot: + name: "flyte-copilot-" + image: "cr.flyte.org/flyteorg/flytecopilot:v0.0.15" + start-timeout: "30s" + default-pod-template-name: #. **Create a PodTemplate resource:** Flyte recognizes PodTemplate definitions with the ``default-pod-template-name`` at two granularities.