Skip to content
New issue

Release 1

Closed Jun 20, 2021 95% complete

MVP 1 scope should include everything which is necessary to handle the following "Namespaced" resources using API

  • Topics, Connects, ACLs

Following "Non-namespaced" resources must be included as well :

  • Namespaces, RoleBindings, TopicValidators, ConnectValidators
    although it is accepted to include some resource "within" Namespace object for now.

Finally…

MVP 1 scope should include everything which is necessary to handle the following "Namespaced" resources using API

  • Topics, Connects, ACLs

Following "Non-namespaced" resources must be included as well :

  • Namespaces, RoleBindings, TopicValidators, ConnectValidators
    although it is accepted to include some resource "within" Namespace object for now.

Finally, a CLI must exist and be able to parse YAML configuration files and discover by itself the API links to perform the main feature of ns4kafka :
kafkactl apply -f {[ file_or_folder }}

where {{ file_or_folder }} is a path to a file or folder containing yaml descriptor files such as :

---
apiVersion: v1
kind: AccessControlEntry
metadata:
  name: f4m-5af5d46a
spec:
  resourceType: TOPIC
  resource: priv_f4m_demo1
  resourcePatternType: LITERAL
  permission: WRITE
  grantedTo: target-ns
---
apiVersion: v1
kind: Topic
metadata:
  name: priv_f4m_demo1
spec:
  replicationFactor: 3
  partitions: 3
  configs:
    min.insync.replicas: '2'
    cleanup.policy: delete
    retention.ms: '60000'
---
apiVersion: v1
kind: Connector
metadata:
  name: "priv_f4m_julien_test"
spec:
  name: priv_f4m_julien_test
  connector.class: org.apache.kafka.connect.file.FileStreamSinkConnector
  tasks.max: '1'
  file: "/tmp/file1"
  topics: connect-test
  value.converter: org.apache.kafka.connect.storage.StringConverter
  key.converter: org.apache.kafka.connect.storage.StringConverter
  consumer.override.sasl.jaas.config: fail
Loading