This project is mirrored from https://gitee.com/linuxsuren/octant.git. Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
  1. 21 Feb, 2020 2 commits
  2. 20 Feb, 2020 5 commits
  3. 19 Feb, 2020 7 commits
  4. 18 Feb, 2020 8 commits
  5. 17 Feb, 2020 2 commits
  6. 16 Feb, 2020 4 commits
  7. 15 Feb, 2020 2 commits
  8. 14 Feb, 2020 7 commits
  9. 13 Feb, 2020 2 commits
    • Wayne Witzel III's avatar
      Merge pull request #683 from mothership/master · 5fcc3e93
      Wayne Witzel III authored
      Fix logs in multi-context environments
      5fcc3e93
    • Jack Wink's avatar
      Fix logs in multi-context environments · 3e0a22ea
      Jack Wink authored
      
      Logging was broken for multi-cluster/multi-context environments.
      Everything else in the dashboard loaded fine, except the logs.
      
      It looks like passing the ClusterClient into the log handler ends up
      caching a pointer to the original cluster. Once the user has switched
      contexts from the UI, the underlying ClusterClient object is swapped
      out on the dashConfig object. However, the pointer is cached for the
      log handler and it still tries to read from the old cluster.
      
      The fix seems to be passing the dashConfig pointer to the log
      handler, and fetching the client on each call.
      
      Tested against our 5 EKS clusters, and observed that logs were now
      working after switching contexts.
      Signed-off-by: default avatarJack Wink <57678801+mothershipper@users.noreply.github.com>
      3e0a22ea
  10. 12 Feb, 2020 1 commit