RESOLVED: Issues communicating with Kubernetes cluster master nodes
  • Kubernetes Service
  • Dallas
    Frankfurt
    London
  • INC0534087
  • Description

    SERVICES/COMPONENTS AFFECTED:
    - Kubernetes Service
    - Databases for postgreSQL
    - Databases for Redis
    - Databases for Etcd
    - Databases for ElasticSearch
    - Messages for RabbitMQ

    IMPACT:
    - Users are unable to communicate with the IBM Kubernetes Service API endpoint
    - Users may not be able to manage their clusters
    - Existing cluster workloads are not affected
    - Users of the database services listed above cannot provision new instances or take administrative actions on their existing service instances, such as scaling, changing passwords, creating backups, etc.  However, existing instances should still be accessible for normal data operations.

     

    STATUS:

     - 2019-01-15 16:40 UTC - INVESTIGATING - The operations team is investigating the issue.
     - 2019-01-15 16:51 UTC - MITIGATING - Some customers are still impacted; the team is working to mitigate the impact completely.
     - 2019-01-15 17:23 UTC - MITIGATING - Added additional service impacts.
     - 2019-01-15 18:47 UTC - MITIGATING - Refined the impact statement for affected Compose services.
     - 2019-01-15 18:27 UTC - MITIGATING - Impact to the data service offerings listed has been resolved as 17:50 UTC.
     - 2019-01-15 19:74 UTC - MONITORING - Customer impact has been eliminated, however the team continues to monitor the system closely.

      - 2019-01-15 21:32 UTC - MONITORING - Added additional region impacts to notification.

     - 2019-01-16  00:37 UTC - SRE Resolved