kubesphere-devops-tenant

You can trigger KubeSphere DevOps pipelines as a namespace tenant by using KubeSphere APIs with OAuth-based authentication, which enforces workspace and namespace isolation without requiring cluster-admin access.

Yes, you can retrieve pipeline logs and artifacts from KubeSphere DevOps as a non-admin user by using the tenant-scoped kapis endpoints with OAuth authentication to maintain namespace isolation.

Workspace and namespace isolation for KubeSphere DevOps tenant operations works by using workspace and namespace-scoped kapis endpoints with OAuth authentication, restricting tenant access to resources within their own namespace.

Yes, you need OAuth authentication to list pipelines and runs in KubeSphere DevOps, as it secures the kapis endpoints and enforces namespace-scoped tenant isolation for pipeline management.

Within a single namespace, you can perform KubeSphere DevOps tenant operations including listing pipelines, triggering pipeline runs, fetching logs and artifacts, and managing credentials via the DevOps API.

Yes, the kubesphere-devops-tenant Skill supports managing credentials for namespace-scoped pipelines, allowing tenants to handle credential management in tenant contexts via KubeSphere DevOps APIs.