This project is mirrored from https://opendev.org/openstack/magnum.git. Pull mirroring updated .
  1. 11 May, 2021 1 commit
  2. 29 Mar, 2021 1 commit
  3. 02 Mar, 2021 1 commit
  4. 15 Jan, 2021 1 commit
  5. 02 Nov, 2020 1 commit
  6. 16 Jul, 2020 1 commit
  7. 06 May, 2020 3 commits
  8. 27 Apr, 2020 1 commit
  9. 16 Mar, 2020 1 commit
  10. 20 Jan, 2020 12 commits
  11. 23 Dec, 2019 1 commit
    • Feilong Wang's avatar
      Fix proxy issue for k8s fedora drivers · 57479b18
      Feilong Wang authored
      Due to the big changes recently to support k8s rolling upgrade, a
      regression issue was introduced which is broken the proxy function
      for image downloading. This patch fixes it for both fedor atomic
      driver and fedora coreos driver.
      
      Task: 37784
      Story: 2007005
      
      Change-Id: I11113d69629e1a97a58e5270f67c7404292b45c3
      (cherry picked from commit ad2ef496)
      57479b18
  12. 17 Dec, 2019 1 commit
    • Diogo Guerra's avatar
      [k8s] Update metrics-server · da2474e3
      Diogo Guerra authored
      
      
      Magnum allows to use CONTAINER_INFRA_PREFIX to specify a local
      repository from which we can pull container images. This repository
      defaults to the upstream one that is specified in the metrics helm
      chart.
      
      * This patch allows for the usage of CONTAINER_INFRA_PREFIX to
      correctly configure the pull of the metric-server container image
      from the specified repo.
      * Add label metrics_server_chart_tag to allow user to specify
      stable/metrics-server chart tag to use
      * Add label metrics_server_enabled to allow enable/disable of
      component (defaults: true)
      
      Story: 2004816
      Task: 37390
      
      Change-Id: Idc315937a82317b76349bbe8466d900d00194953
      Signed-off-by: default avatarDiogo Guerra <dy090.guerra@gmail.com>
      (cherry picked from commit df52f9c9)
      da2474e3
  13. 12 Dec, 2019 1 commit
  14. 11 Dec, 2019 1 commit
    • Diogo Guerra's avatar
      Add prometheus-adapter · 47a86d47
      Diogo Guerra authored
      
      
      This will install the prometheus-adapter stable
      helm chart. Requires monitoring_enabled=true.
      
      The chart version can be configured using
      prometheus_adapter_chart_tag and an option is
      available to overwrite the default configuration
      rules for a user defined ConfigMap referenced
      by using prometheus_adapter_configmap label.
      
      story: 2006765
      task: 37278
      
      Change-Id: I5b86f4455f88c8dbeac6e56942e1ca55f1d1726c
      Signed-off-by: Diogo Filipe Tomas Guerra's avatarDiogo Guerra <diogo.filipe.tomas.guerra@cern.ch>
      (cherry picked from commit 35457580)
      47a86d47
  15. 06 Dec, 2019 1 commit
    • Bharat Kunwar's avatar
      Add nginx_ingress_controller_chart_tag · 1c568721
      Bharat Kunwar authored
      Additioanlly, bumping up the Chart version to 1.24.7 without which the
      ingress controller fails to deploy on 1.16.x.
      
      Additionally, bump up nginx_ingress_controller_tag version to 0.26.1.
      This is to ensure that we are running an up to date nginx ingress
      controller with fixes for known CVEs.
      
      Story: 2006853
      Task: 37444
      
      Change-Id: Ibf045a06d19b02095e19d9a21d14a91a39a3751c
      (cherry picked from commit 7d6e344f)
      1c568721
  16. 25 Oct, 2019 1 commit
  17. 24 Oct, 2019 1 commit
    • Spyridon Trigazis's avatar
      k8s_fedora: Add use_podman label · dacaeb03
      Spyridon Trigazis authored
      Choose whether system containers etcd, kubernetes and the heat-agent will be
      installed with podman or atomic. This label is relevant for k8s_fedora drivers.
      
      k8s_fedora_atomic_v1 defaults to use_podman=false, meaning atomic will be used
      pulling containers from docker.io/openstackmagnum. use_podman=true is accepted
      as well, which will pull containers by k8s.gcr.io.
      
      k8s_fedora_coreos_v1 defaults and accepts only use_podman=true.
      
      Fix upgrade for k8s_fedora_coreos_v1 and magnum-cordon systemd unit.
      
      Task: 37242
      Story: 2005201
      
      (cherry-picked from aa6b3bbe
      
      )
      Change-Id: I0d5e4e059cd4f0458746df7c09d2fd47c389c6a0
      Signed-off-by: Spyridon Trigazis's avatarSpyros Trigazis <spyridon.trigazis@cern.ch>
      dacaeb03
  18. 17 Oct, 2019 2 commits
    • Theodoros Tsioutsias's avatar
      ng-12: Label nodegroup nodes · b56b164d
      Theodoros Tsioutsias authored and Spyridon Trigazis's avatar Spyridon Trigazis committed
      With this change each node will be labeled with the following:
      * --node-labels=magnum.openstack.org/role=${NODEGROUP_ROLE}
      * --node-labels=magnum.openstack.org/nodegroup=${NODEGROUP_NAME}
      
      (cherry picked from commit 113fdc44)
      Change-Id: Ic410a059b19a1252cdf6eed786964c5c7b03d01c
      b56b164d
    • Spyridon Trigazis's avatar
      Support Fedora CoreOS 30 · 0341f921
      Spyridon Trigazis authored
      
      
      Add fedora coreos driver. To deploy clusters with fedora coreos operators
      or users need to add os_distro=fedora-coreos to the image. The scripts
      to deploy kubernetes on top are the same with fedora atomic. Note that
      this driver has selinux enabled.
      
      The startup of the heat-container-agent uses a workaround to copy the
      SoftwareDeployment credentials to /var/lib/cloud/data/cfn-init-data.
      The fedora coreos driver requires heat train to support ignition.
      
      Task: 29968
      Story: 2005201
      
      Signed-off-by: Spyridon Trigazis's avatarSpyros Trigazis <spyridon.trigazis@cern.ch>
      
      (cherry picked from commit 73dc57c3)
      Change-Id: Iffcaa68d385b1b829b577ebce2df465073dfb5a1
      0341f921
  19. 11 Oct, 2019 1 commit
  20. 20 Sep, 2019 1 commit
    • Mohammed Naser's avatar
      [fedora atomic k8s] Add boot from volume support · cfe2753f
      Mohammed Naser authored
      
      
      Support boot from volume for Kubernetes all nodes (master and worker)
      so that user can create a big size root volume, which could be more
      flexible than using docker_volume_size. And user can specify the
      volume type so that user can leverage high performance storage, e.g.
      NVMe etc.
      
      And a new label etcd_volme_type is added as well so that user can
      set volume type for etcd volume.
      
      If the boot_volume_type or etcd_volume_type are not passed by labels,
      Magnum will try to read them from config option
      default_boot_volume_type and default_etcd_volume_type. A random
      volume type from Cinder will be used if those options are not set.
      
      Task: 30374
      Story: 2005386
      
      Co-Authorized-By: default avatarFeilong <Wang&lt;flwang@catalyst.net.nz>
      
      Change-Id: I39dd456bfa285bf06dd948d11c86867fc03d5afb
      cfe2753f
  21. 26 Aug, 2019 1 commit
    • Bharat Kunwar's avatar
      Convert network UUID to name required for OCCM · e84cc4c9
      Bharat Kunwar authored
      Sometimes, the fixed_network value gets rendered as UUID. However OCCM's
      internal-network-name requires the network name, it does not support
      UUID. This patch introduces a new parameter called fixed_network_name
      which converts fixed_network UUID to name if it is UUID-like.
      
      Story: 2005333
      Task: 36313
      
      Change-Id: I3453bc0dbea285687d39c9782685cb1f2a3ecd39
      e84cc4c9
  22. 07 Aug, 2019 1 commit
    • Mohammed Naser's avatar
      k8s: stop introspecting instance name · 2f2d05c8
      Mohammed Naser authored
      We kept introspecting the name of the instance with the assumption
      that the network always existed under .novalocal
      
      This is not always the case, with certain variables changed inside
      Neutron it is possible to control this, therefore, leading in failing
      deploys.
      
      With this change, we pass the instance name directly to the cluster
      and therefore we always have the accurate name.
      
      Task: 36160
      Story: 2006371
      
      Change-Id: I2ba32844b822ffc14da043e6ef7d071bb62a22ee
      2f2d05c8
  23. 29 Jul, 2019 1 commit
    • Bharat Kunwar's avatar
      Add network config to stabilise multi-NIC scenario · 425fb0fa
      Bharat Kunwar authored
      When there is more than one NIC attached to an instance, openstack cloud
      provider returns a random InternalIP back to the host resulting in instability
      with API server which only talks to a default interface.
      
      This patch incorporates the changes made in
      https://github.com/kubernetes/cloud-provider-openstack/pull/444 which enables
      OpenStack Cloud Controller Manager (OCCM) to respect the
      `internal-network-name` in cloud-config file which ensures that InternalIP
      remains stable.
      
      Uses a separate cloud-config file for OCCM to ensure in-tree Cinder volumes
      remain compatible.
      
      Change-Id: Idfa52ed2d512e7dc383a556371e896205dd542f9
      Story: 2005333
      Task: 30271
      425fb0fa
  24. 24 Jul, 2019 1 commit
  25. 25 Jun, 2019 1 commit
    • Diogo Guerra's avatar
      [k8s] Update prometheus monitoring helm based configuration · 41b83cef
      Diogo Guerra authored and Diogo Filipe Tomas Guerra's avatar Diogo Filipe Tomas Guerra committed
      * prometheus-operator chart version upgraded from 0.1.31. to 5.12.3
      * Fix an issue where when using Feature Gate Priority the scheduler
      would evict the prometheus monitoring node-exporter pods
      * Fix an issue where intensive CPU utilization would make the
      metrics fail intermitently or completly fail
      * Prometheus resources are now calculated based on the MAX_NODE_COUNT
      requested
      * Change the sampling rate from the standard 30s to 1 minute (Rollback)
      * Add the missing tiller CONTAINER_INFRA_PREFIX variable to the ConfigMap
      * Add label prometheus_operator_chart_tag to enable the user to
      specify the stable/prometheus-operator chart to use
      * Fix breaking changes on CoreDNS metrics introduced by
      https://github.com/openstack/magnum/commit/8fb27da2fc39c8be32ec756c1cc3779ae07d30a4
      
      
      * Fix Graphana dashboard not showing data.
      
      
      Change-Id: If42873cd6668c07e4e911e4eef5e4ae2232be66f
      Task: 30777
      Task: 30779
      Story: 2005588
      Signed-off-by: default avatarDiogo Guerra <dy090.guerra@gmail.com>
      41b83cef
  26. 20 Jun, 2019 1 commit