adding livenessProbe and readinessProbe in deployment.yaml for porch …

[mansoor17syed]

…server

[nephio-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mansoor17syed
Once this PR has been reviewed and has the lgtm label, please assign kispaljr for approval by writing /assign @kispaljr in a comment. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Catalin-Stratulat-Ericsson]

1. Looks good but if im not mistaken this will only add the readiness probe to the development deployment of porch and not to the deployment of porch in catalog.
2. Changes made in the Yaml files for deploying porch should be replicated across to the catalog porch deployment here to match https://github.com/nephio-project/catalog/tree/main/nephio/core/porch and here also https://github.com/nephio-project/catalog/tree/main/nephio/optional/porch-cert-manager-webhook
3. To explain basically there are 3 porch deployment packages. The one used for the development deployment which you are changing here, the one used by the typical user of porch which is gotten from the catalog in /main/nephio/core/porch and lastly in /main/nephio/optional/porch-cert-manager-webhook which is a porch deployment using cert manager to handle some certificates.
4. its likely that at the very least a new PR needs to be created for adding those changes there along with this. or if the liveliness probe is not required in the development deployment of porch this PR could possibly be closed and only the catalog PR to be merged.
5. Here is an example of a PR where i had made changes to the RBAC in the yaml of the deployment and had to replicate those changes in a different PR for the catalog deployment files to match. PR#126

[kispaljr]

2. Changes made in the Yaml files for deploying porch should be replicated across to the catalog porch deployment here to match https://github.com/nephio-project/catalog/tree/main/nephio/core/porch and here also https://github.com/nephio-project/catalog/tree/main/nephio/optional/porch-cert-manager-webhook

Yes, that is unfortunately true for now.

IMHO this should be automated. It would be nice to have a GitHub action doing this automatically, maybe something similar to the "release" action, that generates a deployment kpt package as a release asset:

porch/.github/workflows/release.yaml

Line 45 in 9b4e226

run: PATH=./bin:$PATH IMAGE_REPO=docker.io/nephio IMAGE_TAG=${{ github.ref_name }} make deployment-config