...
| Ref # | Category | Sub-category | Description | Specification Reference | Notes and GitHub Issue link |
|---|---|---|---|---|---|
req.gen.cnt.02 | General | Cloud nativeness | The Architecture must support immutable infrastructure. | ra2.ch.017 | Need Kubernetes reference to definition of immutable Essentially, configuration is not changed once deployed What does this apply to? Workloads? Are there test cases for this? OK |
req.gen.cnt.03 | General | Cloud nativeness | The Architecture must run conformant Kubernetes as defined by the CNCF. | ra2.k8s.001 | OK |
req.gen.cnt.04 | General | Cloud nativeness | The Architecture must support clearly defined abstraction layers. | Seems vague. What does "abstraction layer" mean specifically? Hardware abstraction?
Link to the GitHub issue: https://github.com/cntt-n/CNTT/issues/2551 NO | |
req.gen.cnt.05 | General | Cloud nativeness | The Architecture should support configuration of all components in an automated manner using openly published API definitions. | ||
req.gen.scl.01 | General | Scalability | The Architecture should support policy driven horizontal auto-scaling of workloads. | ||
req.gen.rsl.01 | General | Resiliency | The Architecture must support resilient Kubernetes components that are required for the continued availability of running workloads. | ra2.k8s.004 | Note: additional detail in link. |
req.gen.rsl.02 | General | Resiliency | The Architecture should support resilient Kubernetes service components that are not subject to req.gen.rsl.01. | ra2.k8s.002 ra2.k8s.003 | OK |
req.gen.avl.01 | General | Availability | The Architecture must provide High Availability for Kubernetes components. | ra2.k8s.002 ra2.k8s.003 ra2.k8s.004 | OK |
req.gen.ost.01 | General | Openness | The Architecture should embrace open-based standards and technologies. | ra2.crt.001 ra2.crt.002 ra2.ntw.002 ra2.ntw.006 ra2.ntw.007 | |
req.inf.com.01 | Infrastructure | Compute | The Architecture must provide compute resources for Pods. | ra2.k8s.004 | OK |
req.inf.stg.01 | Infrastructure | Storage | The Architecture must support the ability for an operator to choose whether or not to deploy persistent storage for Pods. | ra2.stg.004 | OK |
req.inf.ntw.01 | Infrastructure | Network | The Architecture must support network resiliency on the Kubernetes nodes. | No link for additional detail. What does "network resiliency mean, specifially?". What is the configuration? How many nodes, etc.
NO | |
req.inf.ntw.02 | Infrastructure | Network | The Architecture must support fully redundant network connectivity to the Kubernetes nodes, leveraging multiple network connections. | Seems vague. Need more definition. Possibly redundant to HA requirement. No link. Pankaj says that there is a reference that provides additional detail (ra2.ch.013 Sect 4.2 of the RA-2 document)
https://github.com/cntt-n/CNTT/issues/2548 NO | |
req.inf.ntw.03 | Infrastructure | Network | The networking solution should be able to be centrally administrated and configured. | ra2.ntw.001 ra2.ntw.004 | |
req.inf.ntw.04 | Infrastructure | Network | The Architecture must support dual stack IPv4 and IPv6 for Kubernetes workloads. | ra2.ch.007 ra2.k8s.010 | OK |
req.inf.ntw.05 | Infrastructure | Network | The Architecture must support capabilities for integrating SDN controllers. | OK | |
req.inf.ntw.06 | Infrastructure | Network | The Architecture must support more than one networking solution. | ra2.ntw.005 ra2.ntw.007 | OK |
req.inf.ntw.07 | Infrastructure | Network | The Architecture must support the ability for an operator to choose whether or not to deploy more than one networking solution. | ra2.ntw.005 | OK |
req.inf.ntw.08 | Infrastructure | Network | The Architecture must provide a default network which implements the Kubernetes network model. | ra2.ntw.002 | OK |
req.inf.ntw.09 | Infrastructure | Network | The networking solution must not interfere with or cause interference to any interface or network it does not own. | OK | |
req.inf.ntw.10 | Infrastructure | Network | The Architecture must support Cluster wide coordination of IP address assignment. | Need a link with more detail.
| |
req.inf.ntw.13 | Infrastructure | Network | The platform must allow specifying multiple separate IP pools. Tenants are required to select at least one IP pool that is different from the control infrastructure IP pool or other tenant IP pools. | More specifics are being developed as a PR. Requires an IPAM CNI Testability is dependent on API. 2 step process 1. Verify existence of the CNI (optional) 2. Test CNI APIs This is ok if there is a common way to test this. OR if the reqs specify a specific implementation. If someone brings another CNI, they must also bring sufficient test cases - i.e. test coverage is a requirement for CNIs to be considered for inclusion in RI/to be "Anuket compliant". OK - Once PR is complete. | |
req.inf.ntw.14 | Infrastructure | Network | The platform must allow NATless traffic (i.e. exposing the pod IP address directly to the outside), allowing source and destination IP addresses to be preserved in the traffic headers from workloads to external networks. This is needed e.g. for signaling applications, using SIP and Diameter protocols. | ra2.ntw.011 |
Cedric to verify and Update this cell. |
req.inf.vir.01 | Infrastructure | Virtual Infrastructure | The Architecture must support the capability for Containers to consume infrastructure resources abstracted by Host Operating Systems that are running within a virtual machine. | ra2.ch.005 ra2.ch.011 | OK |
req.inf.phy.01 | Infrastructure | Physical Infrastructure | The Architecture must support the capability for Containers to consume infrastructure resources abstracted by Host Operating Systems that are running within a physical server. | Bare metal
Opened an Issue # 2557 and PR #2561 for the missing spec for "Bare Metal" add ra2.ch.008 spec to the reqt Per Specification: The physical machines on which the Kubernetes Nodes run must be equipped with at least 2 physical sockets, each of at least 20 CPU cores. | |
req.kcm.gen.01 | Kubernetes Cluster | General | The Architecture must support policy driven horizontal auto-scaling of Kubernetes Cluster. |
Link to the GitHub issue - https://github.com/cntt-n/CNTT/issues/2563 | |
req.kcm.gen.02 | Kubernetes Cluster | General | The Architecture must enable workload resiliency. | ra2.k8s.004 | 2 Votes OK OK |
req.int.api.01 | API | General | The Architecture must leverage the Kubernetes APIs to discover and declaratively manage compute (virtual and bare metal resources), network, and storage. | For Networking: Compute/storage not yet met. | An Issue is already opened regarding defining/listing Storage types Active PR being worked/not yet approved (2480) John Hartley is working on RM storage Spec and will then work RA1/RA2 |
req.int.api.02 | API | General | The Architecture must support the usage of a Kubernetes Application package manager using the Kubernetes API, like Helm v3. | ra2.pkg.001 | Already part of RC-2 in Functest VIMS 1 line change will be incorporate in RC-2 if the test cases is not disruptive/destructive. OK |
req.int.api.03 | API | General | The Architecture must support stable features in its APIs. | Not Testable. Need to specific a set of stable features/APIs and define what stable means for each API/Feature Consider Removal | |
req.int.api.03 | API | General | The Architecture must support limited backward compatibility in its APIs. Support for the whole API must not be dropped, but the schema or other details can change. | Requirement needs to be rewritten. Vague. May be what K8s would have developed as part of their goals. This is a requirement for the projects. if is a default for K8s why are we specifying it in Anuket. Need a broader audience for context. Next session? |
...