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

feat: Add new Chart for memos #99

Merged
merged 9 commits into from
Mar 15, 2025
Merged

feat: Add new Chart for memos #99

merged 9 commits into from
Mar 15, 2025

Conversation

rm3l
Copy link
Owner

@rm3l rm3l commented Mar 15, 2025

@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

@@ -0,0 +1,83 @@
apiVersion: apps/v1

Check warning

Code scanning / kube-linter

Indicates when containers are running without a read-only root filesystem. Warning

container "memos" does not have a read-only root file system
object: /test-release-memos apps/v1, Kind=Deployment
@@ -0,0 +1,83 @@
apiVersion: apps/v1

Check warning

Code scanning / kube-linter

Indicates when containers are not set to runAsNonRoot. Warning

container "memos" is not set to runAsNonRoot
object: /test-release-memos apps/v1, Kind=Deployment
@@ -0,0 +1,83 @@
apiVersion: apps/v1

Check warning

Code scanning / kube-linter

Indicates when containers do not have CPU requests and limits set. Warning

container "memos" has cpu request 0
object: /test-release-memos apps/v1, Kind=Deployment
@@ -0,0 +1,83 @@
apiVersion: apps/v1

Check warning

Code scanning / kube-linter

Indicates when containers do not have memory requests and limits set. Warning

container "memos" has memory limit 0
object: /test-release-memos apps/v1, Kind=Deployment
@@ -0,0 +1,15 @@
apiVersion: v1

Check warning

Code scanning / kube-linter

Indicates when a deployment-like object is running a container with an invalid container image Warning test

The container "wget" is using an invalid container image, "busybox". Please use images that are not blocked by the BlockList criteria : [".:(latest)$" "^[^:]$" "(.*/[^:]+)$"]
object: /test-release-memos-test-connection /v1, Kind=Pod
@@ -0,0 +1,15 @@
apiVersion: v1

Check warning

Code scanning / kube-linter

Indicates when containers are running without a read-only root filesystem. Warning test

container "wget" does not have a read-only root file system
object: /test-release-memos-test-connection /v1, Kind=Pod
@@ -0,0 +1,15 @@
apiVersion: v1

Check warning

Code scanning / kube-linter

Indicates when containers are not set to runAsNonRoot. Warning test

container "wget" is not set to runAsNonRoot
object: /test-release-memos-test-connection /v1, Kind=Pod
@@ -0,0 +1,15 @@
apiVersion: v1

Check warning

Code scanning / kube-linter

Indicates when containers do not have CPU requests and limits set. Warning test

container "wget" has cpu request 0
object: /test-release-memos-test-connection /v1, Kind=Pod
@@ -0,0 +1,15 @@
apiVersion: v1

Check warning

Code scanning / kube-linter

Indicates when containers do not have memory requests and limits set. Warning test

container "wget" has memory limit 0
object: /test-release-memos-test-connection /v1, Kind=Pod
@rm3l rm3l merged commit 4683f38 into main Mar 15, 2025
19 checks passed
@rm3l rm3l deleted the add_chart_memos branch March 15, 2025 23:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant