Uploaded image for project: 'Logging analytics'
  1. Logging analytics
  2. LOG-341

Run CD jenkins/kibana from our own Kubernetes deployment - not off docker compose

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • El Alto Release
    • None
    • None

      The CD build with heatlhcheck and minimal (vFirewall run - as much as is automated) - is then run on this single commit trigger or set of triggers for the past hour - later the JobBuilder marks the gerrit reviews as passed/failed based on the CD run

      A CD poc running on AWS EC2 is currently up that does part of this (jenkins, elk stack , cd server to run OOM) - but it needs to be finished and migrated into the LF infrastructure
      OOM-393OOM-540

       Work items

      I should be running all our RI CD infrastructure off kubernetes (eating our own dog food) - instead of running the 4 docker images for jenkins, logstash, elasticsearch, kibana in old-school docker-compose templates

      I'll merge the m4.xlarge and r4.large instances in one rancher deployment

       

       

            michaelobrien michaelobrien
            michaelobrien michaelobrien
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: