You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Attila Sasvari (JIRA)" <ji...@apache.org> on 2018/09/09 12:17:00 UTC
[jira] [Created] (KAFKA-7392) Allow to specify subnet for Docker
containers using standard CIDR notation
Attila Sasvari created KAFKA-7392:
-------------------------------------
Summary: Allow to specify subnet for Docker containers using standard CIDR notation
Key: KAFKA-7392
URL: https://issues.apache.org/jira/browse/KAFKA-7392
Project: Kafka
Issue Type: Improvement
Components: system tests
Reporter: Attila Sasvari
During Kafka system test execution, the IP range of the Docker subnet, 'ducknet' is allocated by Docker.
{code}
docker network inspect ducknet
[
{
"Name": "ducknet",
"Id": "f4325c524feee777817b9cc57b91634e20de96127409c1906c2c156bfeb4beeb",
"Created": "2018-09-09T11:53:40.4332613Z",
"Scope": "local",
"Driver": "bridge",
"EnableIPv6": false,
"IPAM": {
"Driver": "default",
"Options": {},
"Config": [
{
"Subnet": "172.23.0.0/16",
"Gateway": "172.23.0.1"
}
]
},
{code}
The default bridge (docker0) can be controlled [externally|https://success.docker.com/article/how-do-i-configure-the-default-bridge-docker0-network-for-docker-engine-to-a-different-subnet] through etc/docker/daemon.json, however, subnet created by ducknet is not. It might be a problem as many businesses make extensive use of the [RFC1918|https://tools.ietf.org/html/rfc1918] private address space (such as 172.16.0.0/12 : 172.16.0.0 - 172.31.255.255) for internal networks (e.g. VPN).
h4. Proposed changes:
- Introduce a new subnet argument that can be used by {{ducker-ak up}} to specify IP range using standard CIDR, extend help message with the following:
{code}
If --subnet is specified, default Docker subnet is overriden by given IP address and netmask,
using standard CIDR notation. For example: 192.168.1.5/24.
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)