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

use k8s resource to keep the status of the ports #6

Open
2 tasks
nyrahul opened this issue Jun 22, 2023 · 2 comments
Open
2 tasks

use k8s resource to keep the status of the ports #6

nyrahul opened this issue Jun 22, 2023 · 2 comments

Comments

@nyrahul
Copy link
Contributor

nyrahul commented Jun 22, 2023

  • The best way to keep the KubeTLS report is in a k8s CRD.
  • The job itself should be converted to CronJob.
  • The Resource should contain:
    • Report time
    • y
    • z

Tasks:

  • Create k8s CRD
  • convert current k8s Job to k8s CronJob
  • [ ]
@cloud-66
Copy link

cloud-66 commented Jul 28, 2023

@nyrahul Hello, thanks for tool. Any plan how to get alert from this statuses if there is non-tls uses ?

@nyrahul
Copy link
Contributor Author

nyrahul commented Jul 30, 2023

The report generates a json,csv report inside the job that can be used by the users to know the status.
However, the challenge is that once the job is Completed, the container local file system cannot be accessed. Typically what others (for e.g., KubeBench) do is to let the user mount a PV inside the pod and specify the volume mount point path for target report data.

Is there any easy way to export the data?

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

No branches or pull requests

2 participants