docs: Document the need to create new jobs upon branching (#2912)

Signed-off-by: Stephen Finucane <[email protected]>

Author: stephenfin

docs/release-procedure.md

@@ -39,8 +39,12 @@ critical bug fixes.
     $ git push origin release-X.Y
     ```
 
-5. new [Docker images](https://console.cloud.google.com/gcr/images/k8s-staging-provider-os) will be builded.
+    New [Docker images](https://console.cloud.google.com/gcr/images/k8s-staging-provider-os) will be built.
 
 6. Make PR modifying [images.yaml](https://github.com/kubernetes/k8s.io/blob/main/registry.k8s.io/images/k8s-staging-provider-os/images.yaml) to promote gcr.io images to registry.k8s.io. The point is to copy the proper image sha256 hashes from the staging repository to the images.yaml.
 
 7. Once images are promoted create release notes using the "Generate release notes" button in the GitHub "New release" UI and publish the release.
+
+8. Update `kubernetes/test-infra` to add jobs for the new release branch in the [`config/jobs/kubernetes/cloud-provider-openstack`](https://github.com/kubernetes/test-infra/tree/master/config/jobs/kubernetes/cloud-provider-openstack) directory.
+
+    This is generally as simple as copying the `release-master` file to `release-X.Y`, adding `--release-XY` suffixes to the job names and `testgrid-tab-name` annotations, and updating the branch specifiers.