Add isNamespaced flag to values.yaml and update related templates and code

Type

Enhancement, Tests

Description

Added support for running the application in a namespaced environment. This is controlled by a new flag isNamespaced in values.yaml.
Updated the main application and the rule binding store to use a new environment variable STORE_NAMESPACE to store the namespace.
Updated the Helm templates to support running in a namespaced environment.
Added a new GitHub Actions workflow for running system tests in a namespaced environment.
Updated the tests for the rule binding store to reflect the changes.

Changes walkthrough

Relevant files

Enhancement

2 files

main.go `Added namespace support in main.go` cmd/main.go - Added a new environment variable `STORE_NAMESPACE` to store the namespace. - Updated the `NewRuleBindingK8sStore` function call to include `storeNamespace`.	+7/-1
store.go `Added namespace support in rule binding store` pkg/rulebindingstore/store.go - Added `storeNamespace` to the `RuleBindingK8sStore` struct. - Updated the `NewRuleBindingK8sStore` function to accept `storeNamespace` as an argument. - Updated the `StartController` function to use `storeNamespace` when creating the informer.	+7/-2

Tests

3 files

store_test.go `Updated tests for rule binding store` pkg/rulebindingstore/store_test.go - Updated the `NewRuleBindingK8sStore` function calls in the tests to include an empty string for `storeNamespace`.	+4/-4
ci.yaml `Added validation for namespaced Helm template in CI workflow` .github/workflows/ci.yaml - Added a new step to validate the namespaced Helm template.	+4/-0
namespaced-system-tests.yaml `Added namespaced system tests workflow` .github/workflows/namespaced-system-tests.yaml - Added a new GitHub Actions workflow for running system tests in a namespaced environment.	+149/-0

Configuration changes

5 files

runtime-rule-binding.crd.yaml `Added namespaced support in CRD` chart/kubecop/crds/runtime-rule-binding.crd.yaml - Added conditional logic to set the scope of the CRD to `Namespaced` if `.Values.isNamespaced` is true.	+4/-1
controller-statefulset.yaml `Added namespaced support in controller statefulset template` chart/kubecop/templates/controller-statefulset.yaml - Added a new environment variable `STORE_NAMESPACE` that gets its value from the pod's namespace if `.Values.isNamespaced` is true.	+6/-0
deamonset.yaml `Added namespaced support in daemonset template` chart/kubecop/templates/deamonset.yaml - Added a new environment variable `STORE_NAMESPACE` that gets its value from the pod's namespace if `.Values.isNamespaced` is true.	+6/-0
default-rule-binding.yaml `Added namespaced support in default rule binding template` chart/kubecop/templates/default-rule-binding.yaml - Added the namespace of the release to the metadata of the default rule binding if `.Values.isNamespaced` is true.	+3/-0
values.yaml `Added namespaced flag in values.yaml` chart/kubecop/values.yaml - Added a new value `isNamespaced` and set it to true.	+2/-0

✨ Usage guide:

**Overview:** The `describe` tool scans the PR code changes, and generates a description for the PR - title, type, summary, walkthrough and labels. The tool can be triggered [automatically](https://github.com/Codium-ai/pr-agent/blob/main/Usage.md#github-app-automatic-tools) every time a new PR is opened, or can be invoked manually by commenting on a PR. When commenting, to edit [configurations](https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml#L46) related to the describe tool (`pr_description` section), use the following template: ``` /describe --pr_description.some_config1=... --pr_description.some_config2=... ``` With a [configuration file](https://github.com/Codium-ai/pr-agent/blob/main/Usage.md#working-with-github-app), use the following template: ``` [pr_description] some_config1=... some_config2=... ```

Enabling\disabling automation

- When you first install the app, the [default mode](https://github.com/Codium-ai/pr-agent/blob/main/Usage.md#github-app-automatic-tools) for the describe tool is: ``` pr_commands = ["/describe --pr_description.add_original_user_description=true" "--pr_description.keep_original_user_title=true", ...] ``` meaning the `describe` tool will run automatically on every PR, will keep the original title, and will add the original user description above the generated description. - Markers are an alternative way to control the generated description, to give maximal control to the user. If you set: ``` pr_commands = ["/describe --pr_description.use_description_markers=true", ...] ``` the tool will replace every marker of the form `pr_agent:marker_name` in the PR description with the relevant content, where `marker_name` is one of the following: - `type`: the PR type. - `summary`: the PR summary. - `walkthrough`: the PR walkthrough. Note that when markers are enabled, if the original PR description does not contain any markers, the tool will not alter the description at all.

Custom labels

The default labels of the `describe` tool are quite generic: [`Bug fix`, `Tests`, `Enhancement`, `Documentation`, `Other`]. If you specify [custom labels](https://github.com/Codium-ai/pr-agent/blob/main/docs/DESCRIBE.md#handle-custom-labels-from-the-repos-labels-page-gem) in the repo's labels page or via configuration file, you can get tailored labels for your use cases. Examples for custom labels: - `Main topic:performance` - pr_agent:The main topic of this PR is performance - `New endpoint` - pr_agent:A new endpoint was added in this PR - `SQL query` - pr_agent:A new SQL query was added in this PR - `Dockerfile changes` - pr_agent:The PR contains changes in the Dockerfile - ... The list above is eclectic, and aims to give an idea of different possibilities. Define custom labels that are relevant for your repo and use cases. Note that Labels are not mutually exclusive, so you can add multiple label categories. Make sure to provide proper title, and a detailed and well-phrased description for each label, so the tool will know when to suggest it.

Inline File Walkthrough 💎

For enhanced user experience, the `describe` tool can add file summaries directly to the "Files changed" tab in the PR page. This will enable you to quickly understand the changes in each file, while reviewing the code changes (diffs). To enable inline file summary, set `pr_description.inline_file_summary` in the configuration file, possible values are: - `'table'`: File changes walkthrough table will be displayed on the top of the "Files changed" tab, in addition to the "Conversation" tab. - `true`: A collapsable file comment with changes title and a changes summary for each file in the PR. - `false` (default): File changes walkthrough will be added only to the "Conversation" tab.

Utilizing extra instructions

The `describe` tool can be configured with extra instructions, to guide the model to a feedback tailored to the needs of your project. Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Notice that the general structure of the description is fixed, and cannot be changed. Extra instructions can change the content or style of each sub-section of the PR description. Examples for extra instructions: ``` [pr_description] extra_instructions=""" - The PR title should be in the format: ': ' - The title should be short and concise (up to 10 words) - ... """ ``` Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable. </details></td></tr> <tr><td><details> <summary><strong> More PR-Agent commands</strong></summary><hr> > To invoke the PR-Agent, add a comment using one of the following commands: > - **/review**: Request a review of your Pull Request. > - **/describe**: Update the PR title and description based on the contents of the PR. > - **/improve [--extended]**: Suggest code improvements. Extended mode provides a higher quality feedback. > - **/ask \<QUESTION\>**: Ask a question about the PR. > - **/update_changelog**: Update the changelog based on the PR's contents. > - **/add_docs** 💎: Generate docstring for new components introduced in the PR. > - **/generate_labels** 💎: Generate labels for the PR based on the PR's contents. > - **/analyze** 💎: Automatically analyzes the PR, and presents changes walkthrough for each component. >See the [tools guide](https://github.com/Codium-ai/pr-agent/blob/main/docs/TOOLS_GUIDE.md) for more details. >To list the possible configuration parameters, add a **/config** comment. </details></td></tr> </table> See the [describe usage](https://github.com/Codium-ai/pr-agent/blob/main/docs/DESCRIBE.md) page for a comprehensive guide on using this tool. </details> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/codiumai-pr-agent-free[bot]"><img src="https://avatars.githubusercontent.com/in/354216?v=4" />codiumai-pr-agent-free[bot]</a> commented <strong> 9 months ago</strong> </div> <div class="markdown-body"> <p><strong><a href="https://github.com/armosec/kubecop/pull/164">PR Description</a></strong> updated to latest commit (<a href="https://github.com/armosec/kubecop/commit/9632dfcf795c6f20fb5336e6b4697899d7ff22ba">https://github.com/armosec/kubecop/commit/9632dfcf795c6f20fb5336e6b4697899d7ff22ba</a>)</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/codiumai-pr-agent-free[bot]"><img src="https://avatars.githubusercontent.com/in/354216?v=4" />codiumai-pr-agent-free[bot]</a> commented <strong> 9 months ago</strong> </div> <div class="markdown-body"> <h2>PR Analysis</h2> <ul> <li>🎯 <strong>Main theme:</strong> Adding support for namespaced environment</li> <li>📝 <strong>PR summary:</strong> This PR introduces a new flag <code>isNamespaced</code> in <code>values.yaml</code> to support running the application in a namespaced environment. It updates the main application and the rule binding store to use a new environment variable <code>STORE_NAMESPACE</code> to store the namespace. It also updates the Helm templates and the tests for the rule binding store to reflect these changes.</li> <li>📌 <strong>Type of PR:</strong> Enhancement</li> <li>🧪 <strong>Relevant tests added:</strong> True</li> <li>⏱️ <strong>Estimated effort to review [1-5]:</strong> 3, because the PR involves changes in multiple files and introduces a new feature. However, the changes are straightforward and well-documented.</li> <li>🔒 <strong>Security concerns:</strong> No security concerns found <h2>PR Feedback</h2></li> </ul> <p><strong>💡 General suggestions:</strong> The PR is well-structured and the changes are clearly explained. It would be beneficial to ensure that the new feature is thoroughly tested in various scenarios to ensure it behaves as expected. Also, it would be good to check if there are any potential edge cases or error conditions that have not been handled.</p> <hr> <details> <summary><strong>✨ Usage guide:</strong></summary><hr> **Overview:** The `review` tool scans the PR code changes, and generates a PR review. The tool can be triggered [automatically](https://github.com/Codium-ai/pr-agent/blob/main/Usage.md#github-app-automatic-tools) every time a new PR is opened, or can be invoked manually by commenting on any PR. When commenting, to edit [configurations](https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml#L19) related to the review tool (`pr_reviewer` section), use the following template: ``` /review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=... ``` With a [configuration file](https://github.com/Codium-ai/pr-agent/blob/main/Usage.md#working-with-github-app), use the following template: ``` [pr_reviewer] some_config1=... some_config2=... ``` <table><tr><td><details> <summary><strong> Utilizing extra instructions</strong></summary><hr> The `review` tool can be configured with extra instructions, which can be used to guide the model to a feedback tailored to the needs of your project. Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify the relevant sub-tool, and the relevant aspects of the PR that you want to emphasize. Examples for extra instructions: ``` [pr_reviewer] # /review # extra_instructions=""" In the 'general suggestions' section, emphasize the following: - Does the code logic cover relevant edge cases? - Is the code logic clear and easy to understand? - Is the code logic efficient? ... """ ``` Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable. </details></td></tr> <tr><td><details> <summary><strong> How to enable\disable automation</strong></summary><hr> - When you first install PR-Agent app, the [default mode](https://github.com/Codium-ai/pr-agent/blob/main/Usage.md#github-app-automatic-tools) for the `review` tool is: ``` pr_commands = ["/review", ...] ``` meaning the `review` tool will run automatically on every PR, with the default configuration. Edit this field to enable/disable the tool, or to change the used configurations </details></td></tr> <tr><td><details> <summary><strong> Auto-labels</strong></summary><hr> The `review` tool can auto-generate two specific types of labels for a PR: - a `possible security issue` label, that detects possible [security issues](https://github.com/Codium-ai/pr-agent/blob/tr/user_description/pr_agent/settings/pr_reviewer_prompts.toml#L136) (`enable_review_labels_security` flag) - a `Review effort [1-5]: x` label, where x is the estimated effort to review the PR (`enable_review_labels_effort` flag) </details></td></tr> <tr><td><details> <summary><strong> Extra sub-tools</strong></summary><hr> The `review` tool provides a collection of possible feedbacks about a PR. It is recommended to review the [possible options](https://github.com/Codium-ai/pr-agent/blob/main/docs/REVIEW.md#enabledisable-features), and choose the ones relevant for your use case. Some of the feature that are disabled by default are quite useful, and should be considered for enabling. For example: `require_score_review`, `require_soc2_ticket`, and more. </details></td></tr> <tr><td><details> <summary><strong> More PR-Agent commands</strong></summary><hr> > To invoke the PR-Agent, add a comment using one of the following commands: > - **/review**: Request a review of your Pull Request. > - **/describe**: Update the PR title and description based on the contents of the PR. > - **/improve [--extended]**: Suggest code improvements. Extended mode provides a higher quality feedback. > - **/ask \<QUESTION\>**: Ask a question about the PR. > - **/update_changelog**: Update the changelog based on the PR's contents. > - **/add_docs** 💎: Generate docstring for new components introduced in the PR. > - **/generate_labels** 💎: Generate labels for the PR based on the PR's contents. > - **/analyze** 💎: Automatically analyzes the PR, and presents changes walkthrough for each component. >See the [tools guide](https://github.com/Codium-ai/pr-agent/blob/main/docs/TOOLS_GUIDE.md) for more details. >To list the possible configuration parameters, add a **/config** comment. </details></td></tr> </table> See the [review usage](https://github.com/Codium-ai/pr-agent/blob/main/docs/REVIEW.md) page for a comprehensive guide on using this tool. </details> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/codiumai-pr-agent-free[bot]"><img src="https://avatars.githubusercontent.com/in/354216?v=4" />codiumai-pr-agent-free[bot]</a> commented <strong> 9 months ago</strong> </div> <div class="markdown-body"> <h2>PR Code Suggestions</h2> <table><thead><tr><th></th><th>Suggestions </th></tr></thead><tbody><tr><td><strong>enhancement</strong></td><td><table><tr><td> <details><summary>Simplify the initialization of <code>storeNamespace</code> by directly assigning it from an environment variable with a default fallback.</summary> ___ **Consider initializing `storeNamespace` with a default value directly instead of setting it <br> to an empty string and then checking for an environment variable. This approach simplifies <br> the code and makes the default behavior more explicit.** [cmd/main.go [150-169]](https://github.com/armosec/kubecop/pull/164/files#diff-c444f711e9191b53952edb65bfd8c644419fc7695c62611dc0fb304b4fb197d6R150-R169) ```diff -storeNamespace := "" -if ns := os.Getenv("STORE_NAMESPACE"); ns != "" { - storeNamespace = ns +storeNamespace := os.Getenv("STORE_NAMESPACE") +if storeNamespace == "" { + storeNamespace = "default" // Or any other default namespace } ``` </details></td></tr></table></td></tr><tr><td><strong>best practice</strong></td><td><table><tr><td> <details><summary>Initialize <code>storeNamespace</code> with a default value in the constructor for consistency.</summary> ___ **Instead of setting `storeNamespace` to `metav1.NamespaceNone` inside the `StartController` <br> method, consider doing this in the `NewRuleBindingK8sStore` constructor. This ensures that <br> the `RuleBindingK8sStore` instance is always correctly initialized before use.** [pkg/rulebindingstore/store.go [196-198]](https://github.com/armosec/kubecop/pull/164/files#diff-4c19cf4bcd9fac5ffcf44014b76e894e889d5a0dd2319e72218064ff96feae55R196-R198) ```diff -if store.storeNamespace == "" { - store.storeNamespace = metav1.NamespaceNone +// This adjustment should be made in the NewRuleBindingK8sStore constructor +if storeNamespace == "" { + storeNamespace = metav1.NamespaceNone +} +ruleBindingStore := RuleBindingK8sStore{ + dynamicClient: dynamicClient, + informerStopChannel: stopCh, + nodeName: nodeName, + coreV1Client: coreV1Client, + storeNamespace: storeNamespace, } ``` </details></td></tr></table></td></tr><tr><td><strong>maintainability</strong></td><td><table><tr><td> <details><summary>Refactor conditional Helm template syntax for <code>isNamespaced</code> to ensure compatibility and avoid errors.</summary> ___ **Ensure that the Helm template syntax for conditionals is correctly used to avoid syntax <br> errors or unexpected behavior when the `isNamespaced` flag is not defined. It's good <br> practice to provide a default value for such flags in the `values.yaml` file or check for <br> existence before using.** [chart/kubecop/crds/runtime-rule-binding.crd.yaml [13-17]](https://github.com/armosec/kubecop/pull/164/files#diff-fd74bc23a77dded82ef08a1d7d69295133cbed6605700fdf3a46708336b0dc31R13-R17) ```diff -{{- if .Values.isNamespaced }} -scope: Namespaced -{{- else }} -scope: Cluster -{{- end }} +scope: {{ if .Values.isNamespaced }}Namespaced{{ else }}Cluster{{ end }} ``` </details></td></tr><tr><td> <details><summary>Use a helper template for setting the <code>STORE_NAMESPACE</code> environment variable to reduce code duplication.</summary> ___ **For better maintainability and to avoid duplication, consider creating a helper template <br> in `_helpers.tpl` that generates the environment variable `STORE_NAMESPACE` if <br> `.Values.isNamespaced` is true. This approach allows you to reuse the logic in both the <br> controller statefulset and daemonset templates without repeating the code.** [chart/kubecop/templates/controller-statefulset.yaml [41-46]](https://github.com/armosec/kubecop/pull/164/files#diff-94879afdd23579720c115da5b7271da861315680ff43c4546e9ef87b19e35c9bR41-R46) ```diff -{{- if .Values.isNamespaced }} -- name: STORE_NAMESPACE - valueFrom: - fieldRef: - fieldPath: metadata.namespace -{{- end }} +{{- include "kubecop.storeNamespaceEnv" . | nindent 10 }} +# Assuming you've defined a template in _helpers.tpl that outputs the STORE_NAMESPACE env variable block if isNamespaced is true. ``` </details></td></tr></table></td></tr><tr><td><strong>reliability</strong></td><td><table><tr><td> <details><summary>Add error handling or retries to the cleanup commands to ensure thorough cleanup.</summary> ___ **To improve the reliability of the cleanup step, consider adding error handling or retries <br> for the commands that might fail due to transient issues. This ensures that the cleanup is <br> as thorough as possible, even if some commands initially fail.** [.github/workflows/namespaced-system-tests.yaml [144-148]](https://github.com/armosec/kubecop/pull/164/files#diff-416d06049e4f75d9aa88496af3a430ffb9bfc83bcc1489914a70cff1035b5789R144-R148) ```diff -helm uninstall kubecop -n kubescape || echo "Failed to uninstall kubecop" -kubectl delete ns kubescape || echo "Failed to delete namespace kubescape" -kubectl delete -f ./chart/kubecop/crds/app-profile.crd.yaml -f ./chart/kubecop/crds/runtime-rule-binding.crd.yaml || echo "Failed to delete crd" -helm uninstall prometheus -n monitoring || echo "Failed to uninstall prometheus" -kubectl delete ns monitoring || echo "Failed to delete namespace monitoring" +# Example of adding a retry loop for helm uninstall +for i in {1..3}; do + helm uninstall kubecop -n kubescape && break || echo "Attempt $i failed to uninstall kubecop" + sleep 5 +done +# Similar retry loops can be added for other commands as needed ``` </details></td></tr></table></td></tr></tr></tbody></table><hr> <details> <summary><strong>✨ Usage guide:</strong></summary><hr> **Overview:** The `improve` tool scans the PR code changes, and automatically generates suggestions for improving the PR code. The tool can be triggered [automatically](https://github.com/Codium-ai/pr-agent/blob/main/Usage.md#github-app-automatic-tools) every time a new PR is opened, or can be invoked manually by commenting on a PR. When commenting, to edit [configurations](https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml#L69) related to the improve tool (`pr_code_suggestions` section), use the following template: ``` /improve --pr_code_suggestions.some_config1=... --pr_code_suggestions.some_config2=... ``` With a [configuration file](https://github.com/Codium-ai/pr-agent/blob/main/Usage.md#working-with-github-app), use the following template: ``` [pr_code_suggestions] some_config1=... some_config2=... ``` <table><tr><td><details> <summary><strong> Enabling\disabling automation </strong></summary><hr> When you first install the app, the [default mode](https://github.com/Codium-ai/pr-agent/blob/main/Usage.md#github-app-automatic-tools) for the improve tool is: ``` pr_commands = ["/improve --pr_code_suggestions.summarize=true", ...] ``` meaning the `improve` tool will run automatically on every PR, with summarization enabled. Delete this line to disable the tool from running automatically. </details></td></tr> <tr><td><details> <summary><strong> Utilizing extra instructions</strong></summary><hr> Extra instructions are very important for the `improve` tool, since they enable to guide the model to suggestions that are more relevant to the specific needs of the project. Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify relevant aspects that you want the model to focus on. Examples for extra instructions: ``` [pr_code_suggestions] # /improve # extra_instructions=""" Emphasize the following aspects: - Does the code logic cover relevant edge cases? - Is the code logic clear and easy to understand? - Is the code logic efficient? ... """ ``` Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable. </details></td></tr> <tr><td><details> <summary><strong> A note on code suggestions quality</strong></summary><hr> - While the current AI for code is getting better and better (GPT-4), it's not flawless. Not all the suggestions will be perfect, and a user should not accept all of them automatically. - Suggestions are not meant to be simplistic. Instead, they aim to give deep feedback and raise questions, ideas and thoughts to the user, who can then use his judgment, experience, and understanding of the code base. - Recommended to use the 'extra_instructions' field to guide the model to suggestions that are more relevant to the specific needs of the project, or use the [custom suggestions :gem:](https://github.com/Codium-ai/pr-agent/blob/main/docs/CUSTOM_SUGGESTIONS.md) tool - With large PRs, best quality will be obtained by using 'improve --extended' mode. </details></td></tr> <tr><td><details> <summary><strong> More PR-Agent commands</strong></summary><hr> > To invoke the PR-Agent, add a comment using one of the following commands: > - **/review**: Request a review of your Pull Request. > - **/describe**: Update the PR title and description based on the contents of the PR. > - **/improve [--extended]**: Suggest code improvements. Extended mode provides a higher quality feedback. > - **/ask \<QUESTION\>**: Ask a question about the PR. > - **/update_changelog**: Update the changelog based on the PR's contents. > - **/add_docs** 💎: Generate docstring for new components introduced in the PR. > - **/generate_labels** 💎: Generate labels for the PR based on the PR's contents. > - **/analyze** 💎: Automatically analyzes the PR, and presents changes walkthrough for each component. >See the [tools guide](https://github.com/Codium-ai/pr-agent/blob/main/docs/TOOLS_GUIDE.md) for more details. >To list the possible configuration parameters, add a **/config** comment. </details></td></tr> </table> See the [improve usage](https://github.com/Codium-ai/pr-agent/blob/main/docs/IMPROVE.md) page for a more comprehensive guide on using this tool. </details> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/amitschendel"><img src="https://avatars.githubusercontent.com/u/58078857?v=4" />amitschendel</a> commented <strong> 9 months ago</strong> </div> <div class="markdown-body"> <p>@Bezbran Can you modify it to not be "store" specific but also applies to application profiles? Like, not just for rule bindings because I want to use this namespace also for application profiles storing.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/Bezbran"><img src="https://avatars.githubusercontent.com/u/5871018?v=4" />Bezbran</a> commented <strong> 9 months ago</strong> </div> <div class="markdown-body"> <blockquote> <p>@Bezbran Can you modify it to not be "store" specific but also applies to application profiles? Like, not just for rule bindings because I want to use this namespace also for application profiles storing.</p> </blockquote> <p>I use "STORE_" to emphasize this is for all objects, not only binding...</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/github-actions[bot]"><img src="https://avatars.githubusercontent.com/in/15368?v=4" />github-actions[bot]</a> commented <strong> 9 months ago</strong> </div> <div class="markdown-body"> <p>:sparkles: Artifacts are available <a href="https://github.com/armosec/kubecop/actions/runs/7774595634">here</a>.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/github-actions[bot]"><img src="https://avatars.githubusercontent.com/in/15368?v=4" />github-actions[bot]</a> commented <strong> 9 months ago</strong> </div> <div class="markdown-body"> <p>:sparkles: Artifacts are available <a href="https://github.com/armosec/kubecop/actions/runs/7774794831">here</a>.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/github-actions[bot]"><img src="https://avatars.githubusercontent.com/in/15368?v=4" />github-actions[bot]</a> commented <strong> 9 months ago</strong> </div> <div class="markdown-body"> <p>:sparkles: Artifacts are available <a href="https://github.com/armosec/kubecop/actions/runs/7780206313">here</a>.</p> </div> </div> <div class="page-bar-simple"> </div> <div class="footer"> <ul class="body"> <li>© <script> document.write(new Date().getFullYear()) </script> Githubissues.</li> <li>Githubissues is a development platform for aggregating issues.</li> </ul> </div> <script src="https://cdn.jsdelivr.net/npm/jquery@3.5.1/dist/jquery.min.js"></script> <script src="/githubissues/assets/js.js"></script> <script src="/githubissues/assets/markdown.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/highlight.min.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/languages/go.min.js"></script> <script> hljs.highlightAll(); </script> </body> </html>

armosec / kubecop