Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update stakater/.github action to v0.0.114 #164

Merged
merged 2 commits into from
Jan 22, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/pull_request.yml
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ on:

jobs:
qa:
uses: stakater/.github/.github/workflows/[email protected].108
uses: stakater/.github/.github/workflows/[email protected].114
with:
MD_CONFIG: .github/md_config.json
DOC_SRC: README.md
Expand Down
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@ The operator's workflow can be described in two different architectural models:

*Cross-Cluster Grafana OnCall Setup:*
For each ManagedClusters identified, the operator communicates with the Grafana Cloud's API, initiating the integration process.
This setup involves creating necessary configurations on Grafana Cloud and retrieving vital details such as the Alertmanager HTTP URL for each respective Spoke cluster.
This setup involves creating necessary configurations on Grafana Cloud and retrieving vital details such as the Alertmanager http URL for each respective Spoke cluster.

*`ManifestWork` Synchronization:*
Utilizing `ManifestWork` resources from open-cluster-management, the operator ensures that alerting configurations are consistent across all Spoke clusters.
Expand Down Expand Up @@ -181,7 +181,7 @@ The operator's workflow can be described in two different architectural models:

*Direct Grafana OnCall Setup:*
Upon identifying the GCC CR, described in the next section, the operator proceeds with the Grafana OnCall setup by interacting with Grafana Cloud's API.
It establishes the necessary integrations and secures essential details, including the Alertmanager HTTP URL.
It establishes the necessary integrations and secures essential details, including the Alertmanager http URL.

*In-Cluster Configuration Management:*
The operator directly applies configuration changes within the cluster, bypassing the need for `ManifestWork`.
Expand Down
Loading