Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Q
QoS Scheduler
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Eclipse Research Labs
CODECO Project
Scheduling and Workload Migration - SWM
QoS Scheduler
Commits
4dff8435
Commit
4dff8435
authored
1 year ago
by
Harald Mueller
Browse files
Options
Downloads
Patches
Plain Diff
Fix network helm
parent
4ee54843
No related branches found
No related tags found
1 merge request
!6
Import v1.3.2 as 2.0.0
Pipeline
#50188
failed
1 year ago
Stage: build
Stage: test
Stage: pr-images
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
helm/qos-scheduler/charts/network/values.yaml
+0
-28
0 additions, 28 deletions
helm/qos-scheduler/charts/network/values.yaml
with
0 additions
and
28 deletions
helm/qos-scheduler/charts/network/values.yaml
+
0
−
28
View file @
4dff8435
...
...
@@ -34,34 +34,6 @@ operators:
image
:
repository
:
network-k8s
# This is a sample operator for a custom network.
# topology:
# command: /bin/network-topology
# pullSecret: qos-registry-access-topology
# networks: ['DEMO']
# The name of the channel controller class to run for this operator.
# This will be passed to the operator using the --channelController flag.
# Currently the only supported values here are is 'base' and 'cnidemo'
# channelControllerImpl: 'cnidemo'
# Use this if you want to configure a cni plugin from your custom network operator.
# The cnidemo channel controller implementation supports the following settings.
# cni:
# The name of the network attachment definition to generate for you.
# This should be unique within your network.
# name: cni-vlan
# The name of your cni plugin. The plugin binary must have been installed in your
# cluster.
# type: 'cni-vlan'
# The cni version of the cni plugin you are using. If you are not sure what to put here,
# inspect your cni plugin.
# This is not the docker image tag of your cni plugin, it is a cni version.
# version: 0.4.0
# The VLAN ID to use for setup of virtual overlay network with sub interface on k8s nodes
# Set to -1 to generate random vlan id
# vlanId: 25
# image:
# repository: network-topology
# This is the l2sm network operator.
l2sm
:
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment