Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
K
k3s
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Jacklull
  • k3s
  • Repository

Switch branch/tag
  • k3s
  • test
  • kubemark
  • gce
  • util.sh
Find file
BlameHistoryPermalink
  • Matt Matejczyk's avatar
    Create the "internal" firewall rule for kubemark master. · 02f28218
    Matt Matejczyk authored Apr 18, 2019
    This is equivalent to the "internal" firewall rule that is created for
    the regular masters.
    The main reason for doing it is to allow prometheus scraping metrics
    from various kubemark master components, e.g. kubelet.
    
    Ref. https://github.com/kubernetes/perf-tests/issues/503
    02f28218
util.sh 5.42 KB
EditWeb IDE

Replace util.sh

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.