Skip to content

Conversation

@Cali0707
Copy link

This PR should bring the remainder of the provider/manager interface changes that we added upstream and unblock #58 and #51

manusa and others added 21 commits October 20, 2025 16:59
…antiations (containers#379)

* refactor(kubernetes): Provider implementations deal with Manager instantiations

Removed `*Manager` parameter from `ProviderFactory`.

Provider implementations should deal with the appropriate (base) Manager instantiation
if needed at all.

Manager creation function divided into two explicit functions:
- NewKubeconfigManager: to be used when using KubeConfig files
- NewInClusterManager: to be used inside a cluster

New functions contain validations to ensure they are used in the expected places.
This ensures that the right manager is used by the provider implementation.

Fake kubeconfig for in-cluster Manager is now generated when the Manager is created.
This kubeconfig has the "magic" strings (inClusterKubeConfigDefaultContext) that are
used by the MCP server and tool mutators.

Signed-off-by: Marc Nuri <[email protected]>

* review: Provider implementation refactor

Signed-off-by: Marc Nuri <[email protected]>

---------

Signed-off-by: Marc Nuri <[email protected]>
…ontainers#388)

Bumps [github.com/mark3labs/mcp-go](https://github.com/mark3labs/mcp-go) from 0.41.1 to 0.42.0.
- [Release notes](https://github.com/mark3labs/mcp-go/releases)
- [Commits](mark3labs/mcp-go@v0.41.1...v0.42.0)

---
updated-dependencies:
- dependency-name: github.com/mark3labs/mcp-go
  dependency-version: 0.42.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…for OIDC (containers#354)

* Initial KinD setup

Signed-off-by: Matthias Wessendorf <[email protected]>

* Initial Keycloak container setup

Signed-off-by: Matthias Wessendorf <[email protected]>

* Adding an initial realm setup

Signed-off-by: Matthias Wessendorf <[email protected]>

* Adding OIDC issuer and realm updates, adding cert-manager and handling self-signed certificates

Signed-off-by: Matthias Wessendorf <[email protected]>

* Updates to script b/c of invalid auth config

Signed-off-by: Matthias Wessendorf <[email protected]>

* Adjusting ports and better support for mac/podman

Signed-off-by: Matthias Wessendorf <[email protected]>

* Addressing review comments:
* do not expose all internal tasks, just keep the important targets documents
* remove the keycloak-forward
* move binaries for dev tools to _output
* generate a configuration TOML file into the _output folder

Signed-off-by: Matthias Wessendorf <[email protected]>

---------

Signed-off-by: Matthias Wessendorf <[email protected]>
* feat(http): add custom CA certificate support for OIDC providers

add support for nodes logs

Signed-off-by: blublinsky <[email protected]>

* removed some tools

Signed-off-by: blublinsky <[email protected]>

---------

Signed-off-by: blublinsky <[email protected]>
Co-authored-by: Matthias Wessendorf <[email protected]>
…#397)

Adds a softlink to AGENTS.md so that CLAUDE can reuse the
information.

Signed-off-by: Marc Nuri <[email protected]>
… overrides (containers#396)

* feat(config): default configuration with merge support for downstream overrides

Creates the required infrastructure for downstream forks to be able to provide
default config overrides without modifying the original source code.

Downstream forks should be able to create merge/rebase scripts that
automatically accepted downstream merge conflicts in config_default_overrides.go
since this file will never change upstream.

Example usage for downstream forks:

To customize defaults, simply populate fields in the returned StaticConfig:

```go
func defaultOverrides() *StaticConfig {
  return &StaticConfig{
    ListOutput: "json",           // Override default list output format
    Toolsets:   []string{"core"}, // Override default enabled toolsets
    Port:       "9000",           // Override default port
  }
}
```

Any fields specified here will override the base defaults defined in config_default.go.
Fields not specified will preserve their base default values.

Signed-off-by: Marc Nuri <[email protected]>

* test: skip downstream toolset (full) tests

Skips toolset metadata tests in case there are config overrides.
This is useful in downstream forks where the default toolsets
might be different to those upstream.

Signed-off-by: Marc Nuri <[email protected]>

---------

Signed-off-by: Marc Nuri <[email protected]>
* fix(nodes): reviewed kubernetes.nodes implementation

- Changed node_log tool name to nodes_log for consistency
- Added access control check for nodes and configured denied resources
- Migrated tests to testify
- Added complete test coverage for nodes_log

https://kubernetes.io/docs/concepts/cluster-administration/system-logs/#log-query

Signed-off-by: Marc Nuri <[email protected]>

* test(nodes): add test for nodes_log tool with negative tail argument

Signed-off-by: Marc Nuri <[email protected]>

---------

Signed-off-by: Marc Nuri <[email protected]>
…ity (containers#400)

* test(pods): update PodsExec tests to use testify and improve readability

Signed-off-by: Marc Nuri <[email protected]>

* review: enhance namespace="" test description for pods_exec clarity

Signed-off-by: Marc Nuri <[email protected]>

---------

Signed-off-by: Marc Nuri <[email protected]>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 24, 2025
@openshift-ci-robot
Copy link

@Cali0707: This pull request explicitly references no jira issue.

In response to this:

This PR should bring the remainder of the provider/manager interface changes that we added upstream and unblock #58 and #51

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@Cali0707
Copy link
Author

/cc @harche @manusa @matzew

@openshift-ci openshift-ci bot requested review from harche and matzew October 24, 2025 19:14
@openshift-ci
Copy link

openshift-ci bot commented Oct 24, 2025

@Cali0707: GitHub didn't allow me to request PR reviews from the following users: manusa.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @harche @manusa @matzew

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci openshift-ci bot requested a review from ardaguclu October 24, 2025 19:14
@openshift-ci
Copy link

openshift-ci bot commented Oct 24, 2025

@Cali0707: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Copy link

@harche harche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 24, 2025
@ardaguclu
Copy link
Member

/approve

@openshift-ci
Copy link

openshift-ci bot commented Oct 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ardaguclu, Cali0707, harche

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 25, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit ce29678 into openshift:main Oct 25, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants