bump kubernetes

[jsbroks]

Summary by CodeRabbit

• New Features

  • Added Kubernetes sync functionality, allowing users to connect to a Kubernetes cluster and list pods via a new sync command.
  • Enhanced ClickHouse sync with richer metadata, improved authentication, and more detailed resource information.

• Refactor

  • Updated ClickHouse sync to use structured API responses and basic authentication with separate API ID and secret.

• Chores

  • Introduced a .gitignore to exclude environment and test script files from version control.
  • Updated dependency declarations for AWS SDK modules in the project configuration.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This update introduces a new Kubernetes sync feature by adding two new files: one for Kubernetes client configuration handling and another for the sync command that lists pods in the default namespace. The sync command registration is updated to include this new Kubernetes subcommand. The ClickHouse sync logic is refactored to support a richer API model, more detailed resource metadata, and switches to basic authentication. A new .gitignore file is added to exclude environment and test files. Additionally, AWS SDK dependencies are promoted to direct dependencies in the go.mod file. Minor formatting changes are made in the EC2 sync code.

Changes

File(s)	Change Summary
.gitignore	Added to ignore .env and test.bash files.
go.mod	Moved AWS SDK v2 dependencies from indirect to direct dependencies.
cmd/ctrlc/root/sync/aws/ec2/ec2.go	Reformatted struct literal for EC2Instance initialization; no logic changes.
cmd/ctrlc/root/sync/clickhouse/clickhouse.go	Refactored ClickHouse client and sync logic: richer API response structs, new authentication (API ID/secret), improved logging, expanded metadata/config, new exported types and methods.
cmd/ctrlc/root/sync/kubernetes/client.go	New file: Implements Kubernetes config loading (env, default path, in-cluster), context/cluster name extraction, and error handling.
cmd/ctrlc/root/sync/kubernetes/kubernetes.go	New file: Adds Cobra command to sync Kubernetes resources by listing pods in the default namespace, with logging and error handling.
cmd/ctrlc/root/sync/sync.go	Registers new Kubernetes sync subcommand with the root sync command. No changes to public APIs.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CobraCmd
    participant KubernetesSyncCmd
    participant KubeConfigHelper
    participant KubeClient
    participant K8sAPI

    User->>CobraCmd: Run `sync kubernetes` command
    CobraCmd->>KubernetesSyncCmd: Execute command handler
    KubernetesSyncCmd->>KubeConfigHelper: getKubeConfig()
    KubeConfigHelper->>KubeConfigHelper: Load config (env, default, in-cluster)
    KubeConfigHelper-->>KubernetesSyncCmd: Return config, cluster name
    KubernetesSyncCmd->>KubeClient: Create clientset
    KubernetesSyncCmd->>K8sAPI: List pods in "default" namespace
    K8sAPI-->>KubernetesSyncCmd: Return pod list
    KubernetesSyncCmd->>User: Print/log pod info

Loading

sequenceDiagram
    participant SyncCmd
    participant ClickHouseClient
    participant ClickHouseAPI
    participant Logger

    SyncCmd->>ClickHouseClient: GetServices()
    ClickHouseClient->>Logger: Log org ID
    ClickHouseClient->>ClickHouseAPI: HTTP GET with basic auth
    ClickHouseAPI-->>ClickHouseClient: Return JSON response
    ClickHouseClient->>Logger: Pretty-print raw JSON
    ClickHouseClient->>ClickHouseClient: Decode to ClickHouseListResponse
    ClickHouseClient-->>SyncCmd: Return list of ClickHouseConfigResponse
    SyncCmd->>Logger: Log and process resources

Loading

Poem

In the garden of code, a new path appears,
Kubernetes joins with pods and cheers!
ClickHouse grows smarter, with secrets in tow,
EC2’s lines are tidy and ready to go.
The rabbit hops on, dependencies in line—
Ignoring secrets, everything’s fine!
With every new sync, the meadow will shine. 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c9daebd and 414548d.

📒 Files selected for processing (7)

• .gitignore (1 hunks)
• cmd/ctrlc/root/sync/aws/ec2/ec2.go (1 hunks)
• cmd/ctrlc/root/sync/clickhouse/clickhouse.go (7 hunks)
• cmd/ctrlc/root/sync/kubernetes/client.go (1 hunks)
• cmd/ctrlc/root/sync/kubernetes/kubernetes.go (1 hunks)
• cmd/ctrlc/root/sync/sync.go (2 hunks)
• go.mod (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.