CodeFlare SDK
An intuitive, easy-to-use python interface for batch resource requesting, access, job submission, and observation. Simplifying the developer's life while enabling access to high-performance compute resources, either in the cloud or on-prem.
For guided demos and basics walkthroughs, check out the following links:
- Guided demo notebooks available here, and copies of the notebooks with expected output also available
- these demos can be copied into your current working directory when using the
codeflare-sdkby using thecodeflare_sdk.copy_demo_nbs()function - Additionally, we have a video walkthrough of these basic demos from June, 2023
Full documentation can be found here
Installation
Can be installed via pip: pip install codeflare-sdk
Authentication
CodeFlare SDK uses kube-authkit for Kubernetes authentication, supporting multiple authentication methods:
- Auto-Detection - Automatically detects kubeconfig or in-cluster authentication
- Token-Based - Authenticate with API server token
- OIDC - OpenID Connect authentication with device flow or client credentials
- OpenShift OAuth - Native OpenShift OAuth support
- Kubeconfig - Traditional kubeconfig file authentication
- In-Cluster - Service account authentication when running in a pod
Quick Start
from kube_authkit import get_k8s_client, AuthConfig
from codeflare_sdk import set_api_client, Cluster, ClusterConfiguration
# Option 1: Auto-detect authentication (recommended - no explicit auth needed!)
cluster = Cluster(ClusterConfiguration(
name='my-cluster',
num_workers=2,
))
cluster.apply()
# Option 2: OIDC authentication
auth_config = AuthConfig(
method="oidc",
oidc_issuer="https://your-oidc-provider.com",
client_id="your-client-id",
use_device_flow=True
)
api_client = get_k8s_client(config=auth_config)
set_api_client(api_client) # Register with CodeFlare SDK
# Option 3: OpenShift OAuth with token
auth_config = AuthConfig(
k8s_api_host="https://api.example.com:6443",
token="your-token"
)
api_client = get_k8s_client(config=auth_config)
set_api_client(api_client) # Register with CodeFlare SDK
# Now create your cluster
cluster = Cluster(ClusterConfiguration(
name='my-cluster',
num_workers=2,
))
cluster.apply()
Migration from Legacy Authentication
If you're using the deprecated TokenAuthentication or KubeConfigFileAuthentication classes, please see our Migration Guide for detailed instructions on updating to kube-authkit.
Legacy classes (deprecated):
# ⚠️ Deprecated - will be removed in v1.0.0
from codeflare_sdk import TokenAuthentication
auth = TokenAuthentication(token="...", server="...")
auth.login()
New recommended approach:
# ✅ Recommended - Auto-detection (no explicit auth needed!)
from codeflare_sdk import Cluster, ClusterConfiguration
cluster = Cluster(ClusterConfiguration(name="my-cluster"))
# ✅ For OIDC or OpenShift OAuth with token
from kube_authkit import AuthConfig, get_k8s_client
from codeflare_sdk import set_api_client
auth_config = AuthConfig(
k8s_api_host="https://api.example.com:6443",
token="your-token"
)
api_client = get_k8s_client(config=auth_config)
set_api_client(api_client) # Register with CodeFlare SDK
Development
Please see our CONTRIBUTING.md for detailed instructions.
Release Instructions
Automated Releases
It is possible to use the Release Github workflow to do the release. This is generally the process we follow for releases
Manual Releases
The following instructions apply when doing release manually. This may be required in instances where the automation is failing.
- Check and update the version in "pyproject.toml" file.
- Commit all the changes to the repository.
- Create Github release (https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release).
- Build the Python package.
poetry build - If not present already, add the API token to Poetry.
poetry config pypi-token.pypi API_TOKEN - Publish the Python package.
poetry publish - Trigger the Publish Documentation workflow
10 maintainers
Release files for codeflare-sdk 0.39.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| codeflare_sdk-0.39.0.tar.gz | 187.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| codeflare_sdk-0.39.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 449.2 kB
Release files / codeflare_sdk-0.39.0.tar.gz
| Download URL | codeflare_sdk-0.39.0.tar.gz |
|---|---|
| Size | 187.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
20d2facfa3eff1a619b4863471498be13b3caeac7d039faedd81f240d0357106
|
|
BLAKE2b-256 checksum How to use checksums |
faaf086abae31cb7fc80f641fc4bc5199ff92c41b43f13bb692248f9898b22fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency logRelease files / codeflare_sdk-0.39.0-py3-none-any.whl
| Download URL | codeflare_sdk-0.39.0-py3-none-any.whl |
|---|---|
| Size | 262.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d80aee516afacc00e8e869e714ecd8492297eed97658a88eda8f6c45c7dcc80a
|
|
BLAKE2b-256 checksum How to use checksums |
598ae15d71cf48fce18e9b7d0062bdb047b0cba336ad2861b17b200ee15c06b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency log
