Config processing tests

[rashmichandrashekar]

PR Description

Adding config processing tests for the scenarios listed here -
https://microsoft.sharepoint.com/teams/ContainerInsights/_layouts/15/Doc.aspx?sourcedoc={dc357060-d7e5-46a6-a599-88ec4fdee1de}&action=edit&wd=target%28Prometheus%20Metrics.one%7C29807f1f-70be-4902-b7f6-75b2540c23d3%2FConfigmap%20testing%20scenarios%7Cbae9a2e2-2b4e-431f-8fb6-6b0de29ae595%2F%29&wdorigin=NavigationUrl

Link to scheduled run - https://github-private.visualstudio.com/azure/_build/results?buildId=96095&view=results
comment: # (The below checklist is for PRs adding new features. If a box is not checked, add a reason why it's not needed.)

New Feature Checklist

• List telemetry added about the feature.
• Link to the one-pager about the feature.
• List any tasks necessary for release (3P docs, AKS RP chart changes, etc.) after merging the PR.
• Attach results of scale and perf testing.

Tests Checklist

• Have end-to-end Ginkgo tests been run on your cluster and passed? To bootstrap your cluster to run the tests, follow these instructions.
  • Labels used when running the tests on your cluster:
    • operator
    • windows
    • arm64
    • arc-extension
    • fips
• Have new tests been added? For features, have tests been added for this feature? For fixes, is there a test that could have caught this issue and could validate that the fix works?
  • Is a new scrape job needed?
    • The scrape job was added to the folder test-cluster-yamls in the correct configmap or as a CR.
  • Was a new test label added?
    • A string constant for the label was added to constants.go.
    • The label and description was added to the test README.
    • The label was added to this PR checklist.
    • The label was added as needed to testkube-test-crs.yaml.
  • Are additional API server permissions needed for the new tests?
    • These permissions have been added to api-server-permissions.yaml.
  • Was a new test suite (a new folder under /tests) added?
    • The new test suite is included in testkube-test-crs.yaml.

[rashmichandrashekar]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[github-actions]

This PR is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[vishiy]

Thanks for adding config proc tests @rashmichandrashekar .

[rashmichandrashekar]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).