This release is a pre-release and may not be stable for production use.
floe-network-security-k8s
Kubernetes Network Security plugin for the floe data platform.
Overview
This plugin implements the NetworkSecurityPlugin interface from floe-core, providing
Kubernetes-native NetworkPolicy and Pod Security manifest generation for:
- Default-deny NetworkPolicies for job and platform namespaces
- Egress allowlists for DNS, catalog, telemetry, and storage services
- Ingress rules for ingress controller and intra-namespace communication
- Pod Security Standards namespace labels (restricted/baseline)
- Hardened container securityContext configurations
Installation
pip install floe-network-security-k8s
Usage
from floe_network_security_k8s import K8sNetworkSecurityPlugin
from floe_core.network import NetworkPolicyConfig
plugin = K8sNetworkSecurityPlugin()
# Generate default-deny policies for a namespace
policies = plugin.generate_default_deny_policies("floe-jobs")
# Generate DNS egress rule (always required)
dns_rule = plugin.generate_dns_egress_rule()
Entry Point
This plugin registers under the floe.network_security entry point group:
[project.entry-points."floe.network_security"]
k8s = "floe_network_security_k8s:K8sNetworkSecurityPlugin"
Requirements
- Python 3.10+
- Kubernetes 1.25+ (for Pod Security Admission controller)
- CNI with NetworkPolicy support (Calico, Cilium, or cloud-native CNI)
- floe-core 0.1.0+
Features
NetworkPolicy Generation
- Default-deny ingress and egress policies
- DNS egress always allowed (UDP 53 to kube-system)
- Platform service egress (Polaris, OTel Collector, MinIO)
- External HTTPS egress (configurable)
- Custom egress rules via manifest.yaml
Pod Security Standards
- Namespace labels for PSS enforcement
- Restricted level for job pods
- Baseline level for platform services
- Audit and warn labels for visibility
Container Hardening
runAsNonRoot: truereadOnlyRootFilesystem: trueallowPrivilegeEscalation: falsecapabilities.drop: ["ALL"]seccompProfile: RuntimeDefault
License
Apache-2.0
Metadata
Release files for floe-network-security-k8s 0.1.0a1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| floe_network_security_k8s-0.1.0a1.tar.gz | 38.0 kB | Without provenance | Details for floe_network_security_k8s-0.1.0a1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| floe_network_security_k8s-0.1.0a1-py3-none-any.whl | Python 3 | none | any | Details for floe_network_security_k8s-0.1.0a1-py3-none-any.whl |
Total release size: 48.3 kB
Release files / floe_network_security_k8s-0.1.0a1.tar.gz
| Download URL | floe_network_security_k8s-0.1.0a1.tar.gz |
|---|---|
| Size | 38.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2af99c805c7539444ffda766facd52961ca3ff5a52d72973009bb3a746469f0
|
|
BLAKE2b-256 checksum How to use checksums |
13c3cb982ad245038fbaeeb4e89075d1e9a340fe72ed41d39d5d01a796d52e86
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Release files / floe_network_security_k8s-0.1.0a1-py3-none-any.whl
| Download URL | floe_network_security_k8s-0.1.0a1-py3-none-any.whl |
|---|---|
| Size | 10.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1554935b194cf7e42632661871ba4588602a7397cdcbaa90d366f3909020a89f
|
|
BLAKE2b-256 checksum How to use checksums |
317d860f7d2276210e749cc53787065bbea8e50528ca421cea49729a38cb0514
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Security for floe-network-security-k8s 0.1.0a1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.