redpanda-operator/acceptance/features/cluster.feature at ad597b949d52d29cad9f177f4335b7300efc97dc · redpanda-data/redpanda-operator · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
# This file contains some tests originally ported from our e2e-v2 tests.
# We should really evaluate whether or not to just delete these.
Feature: Basic cluster tests
  @skip:gke @skip:aks @skip:eks
  Scenario: Updating admin ports
    # replaces e2e-v2 "upgrade-values-check"
    Given I apply Kubernetes manifest:
    """
    ---
    apiVersion: cluster.redpanda.com/v1alpha2
    kind: Redpanda
    metadata:
      name: upgrade
    spec:
      clusterSpec:
        statefulset:
          replicas: 1
        listeners:
          admin:
            external:
              default:
                port: 9645
    """
    And cluster "upgrade" is stable with 1 nodes
    And service "upgrade-external" has named port "admin-default" with value 9645
    And rpk is configured correctly in "upgrade" cluster
    When I apply Kubernetes manifest:
    """
    ---
    apiVersion: cluster.redpanda.com/v1alpha2
    kind: Redpanda
    metadata:
      name: upgrade
    spec:
      clusterSpec:
        statefulset:
          replicas: 1
        listeners:
          admin:
            external:
              default:
                port: 9640
    """
    Then cluster "upgrade" is stable with 1 nodes
    And service "upgrade-external" should have named port "admin-default" with value 9640
    And rpk is configured correctly in "upgrade" cluster